Update build workflow #2003

New Issue

MrUnknownDE · 2026-04-06T02:47:51+02:00

MrUnknownDE commented

2026-04-06 02:47:51 +02:00

Originally created by @BlackDex on 9/15/2022

Currently the branch protection is set on specific workflows which needs to be run every time a PR is created (or a push).

Because it isn't possible to tell the branch protection only to do it's job if specific files are touched or not, we just need to make sure these jobs are always started.

Also, because we now check the builds for an MSRV, and the title would change all the time, that would cause the branch protection to be updated everytime the MSRV would change. This is now also addressed by naming that job 'msrv' instead of the version number.

*Originally created by @BlackDex on 9/15/2022* Currently the branch protection is set on specific workflows which needs to be run every time a PR is created (or a push). Because it isn't possible to tell the branch protection only to do it's job if specific files are touched or not, we just need to make sure these jobs are always started. Also, because we now check the builds for an MSRV, and the title would change all the time, that would cause the branch protection to be updated everytime the MSRV would change. This is now also addressed by naming that job 'msrv' instead of the version number.

MrUnknownDE closed this issue

2026-04-06 02:47:51 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#2003