chore: label and annotate CI deployment namespaces #115
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aledegano
approved these changes
Aug 13, 2025
Contributor
aledegano
left a comment
aledegano
left a comment
There was a problem hiding this comment.
Great idea! Thanks Tasko
Member
Author
|
I will test this out in a PR and then merge it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 will help us to find namespaces for CI deployments quicker. Because right now we have to use some regex to check which namespace is and is not for a CI deployment.
Also if we set the PR_URL env variable in the action then we can have the link to the PR that triggered the CI deployment. Currently we also have to put togther the PR url (from the release name) and check the state of the PR when we clean up.