adds roles to deploy notifications and seperate discord notifications #471
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to clarify what is being deployed, and decrease the noise given by the deploy notifications. This is made possible by:
production
/staging
channel (current), and(production|staging)-deployments
(new). People can mute what they want. This PR supports differentiating the two hooks.The bitwarden secret containing the discord webhook has been updated to reflect both production and staging webhooks.
To satisfy the linter, I renamed the fallacious-rooster role to rooster.
Once merged, I will create two new channels and update the webhooks to point to the new deployments channels.