Hi all,
I encountered some more issues regarding branch protection. Even though
I managed to resolve the main issue (regarding required checks and
required linear history), the current setup still has some drawbacks
that I was not aware of before:
Due to the restriction of requiring specific workflows to pass (and none
of us having admin privileges for the repositories), we are no longer
able to directly push to the protected branch (i.e. the 'master' branch).
While this is not a deal breaker in my opinion, it does make checking in
simple changes more cumbersome (as it requires such changes to also be
proposed as pull requests).
Additionally, this makes it troublesome if the required actions ever
were to break in a manner that can't be fixed by us directly (i.e. due
to an issue with an external dependency), as this would prevent us from
merging pull requests (and thereby checking in any new changes on the
master) on the repositories in the meantime. Such issues can be
circumvented by temporarily enabling 'continue-on-error'
(https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error)
for the affected steps (or replacing them with NOP operations), but it
still creates additional work.
In general, I feel like the topic still merits some discussion, so I
would like for it to be included in the agenda for the next conference call.
Best regards,
Tobias
