Name the Slack channel #ops in the CoP lead onboard template - #217
Merged
Conversation
6 tasks
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.
The "Slack channel membership" checklist in
onboard-devops-cop-lead.mdnames#devops. The channel is#ops— the same defect fixed on the recruit template in #216, found while working #170.Every other reference to it across the org already says
#ops:README.md,CONTRIBUTING.mdandclose-fork-prs.ymlin this repo, the same files indevops-securityandincubator, and five pages of the wiki, all pointing athttps://hackforla.slack.com/archives/CV7QGL66B. These two templates were the only outliers.The consequence is worth stating: this line is a checklist item handed to every incoming CoP lead, so as written it asks them to join a channel under the wrong name.
No ticket — raised directly. GitHub renders issue templates from the default branch only, so this can't be checked from the branch; verify from the rendered template after merge.