Use protected CI environment #25

New Issue

MrUnknownDE · 2026-04-05T20:28:59+02:00

MrUnknownDE commented

2026-04-05 20:28:59 +02:00

Originally created by @dani-garcia on 3/23/2026

I've created a new protected environment that will only apply the secrets to protected branches (main). This should silence some zizmor lints.

I had to remove the top-level env, as the environment seems to only apply to the jobs. Rather than duplicate the HAVE_* variables, I just changed the workflow to check the *_REPO variables only, and updated the comment to mention it.

*Originally created by @dani-garcia on 3/23/2026* I've created a new protected environment that will only apply the secrets to protected branches (`main`). This should silence some zizmor lints. I had to remove the top-level env, as the environment seems to only apply to the jobs. Rather than duplicate the `HAVE_*` variables, I just changed the workflow to check the `*_REPO` variables only, and updated the comment to mention it.

MrUnknownDE closed this issue

2026-04-05 20:28:59 +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#25