Match renamed role: DevOps Engineer label in IAM request template - #194
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Part of hackforla/devops#212.
The label
role: DevOps engineerwas renamed torole: DevOps Engineerto matchdevopsandincubator. Template frontmatter is matched exactly and GitHub silently drops a label it cannot find, so this template would otherwise stop applying a role label.After this merges, open the New Issue picker, submit a test issue from "Request AWS IAM user or service account", and confirm it carries
role: DevOps Engineer— template changes only take effect from the default branch, so this cannot be checked from the branch.