+1

I just had to scroll through 500 messages of @xxx xxx temporarily deployed to xxx in an older PR (dependabot update that broke CI but a later update fixed itself). Is there anyone one can do to supress this message?

+1

If you are setting the environment: in your job / workflow... Removing it will stop GitHub Actions from posting the messages.

@uncledru: If you are setting the environment: in your job / workflow... Removing it will stop GitHub Actions from posting the messages.

While that's true, the environment is also used to provide environment specific Environment variables and Environment secrets, as well as show the status and links to deployed environments.

Practically speaking though, in case of feature environment (i.e. non-[prod|beta|staging] envs), we might get rid of the environment entirely and set its variables and secrets as Repository variables and Repository secrets (to be overridden by said prod, beta and staging envs).

I have just tested with environment: 'My override test' the following:

• setting MY_VAR in both Repository variables and Environment variables
• setting MY_SECRET in both Repository secrets and Environment secrets

And and verified that in both cases the environment specific variable/secret takes precedence over the repository wide version. ✅

I realise this doesn't solve everyone's issues!
But at least it means that for feature branches this approach could work 🙂