Run tests also after merging

[michaelosthege]

Previously tests did not run after merging.

This lead to incompatible changes being merged right after one another.

By running tests on main we will notice breaks earlier.

Other options would be to require every PR to rebase on main before merging. This is known as requiring linear history and can be changed in the project settings.

[michaelosthege]

#135 broke the tests on main when it was merged.

@drbacke under https://github.com/Akkudoktor-EOS/EOS/settings/branches you can create a branch protection rule for main and make these settings to avoid introduction of bugs:

Protect matching branches

• Require a pull request before merging
• Require status checks to pass before merging

Rules applied to everyone including administrators

• Allow force pushes
• Allow deletions

[drbacke]

#135 broke the tests on main when it was merged.

@drbacke under https://github.com/Akkudoktor-EOS/EOS/settings/branches you can create a branch protection rule for main and make these settings to avoid introduction of bugs:

Protect matching branches

• Require a pull request before merging
• Require status checks to pass before merging

Rules applied to everyone including administrators

• Allow force pushes
• Allow deletions

Done😊 Good Idea👍

[michaelosthege]

replaced by #154

[michaelosthege]

@drbacke the branch rules appear to match the test-on-main branch too, preventing me from force-pushing or deleting it.
I moved the changes to a new PR #154. Please delete the test-on-main branch

[drbacke]

@michaelosthege maybe this is too restrictive. But the "Standard" rule doesnt seem to prevent force pushes. Maybe i've configured IT wrong