use pr instead of directly pushing to master

[alex19EP]

hello. this applies to the main team, which has access to push to the master. since we now have a fairly extensive CI with tests, it would be great if all merges into the master branch were done by creating a prs, this will improve visibility and tractability of changes.

[jaacoppi]

I'm guilty! Good idea. Can GitHub Actions force this behavior?

[jaacoppi]

https://stackoverflow.com/questions/46146491/prevent-pushing-to-master-on-github

Some ideas to get started.

[djphoenix]

Indeed good idea.
I’m also propose to perform only fast-forward merges, because some fixes may break the code even if its have no direct conflicts. So rebase-test-merge is preferred way for me (and many other projects). Any objections?

[alex19EP]

I’m also propose to perform only fast-forward merges, because some fixes may break the code even if its have no direct conflicts.

implemented.

@jaacoppi I have now turned on the disallow to override restrictions for administrators option. so I think next time you will see an error when pushing directly to the master.