You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to fix two broken links, two wrong-cased Devops spellings and one wrong Slack channel name in the recruit-new-lead issue template, so that whoever runs a lead recruitment isn't sent to a 404 and the issue it generates spells the team's name the way the rest of the org does. One link points at a classic project board GitHub has retired, the other has an empty target.
Action Items
On line 15, replace the Open Roles board link https://github.com/hackforla/devops/projects/1 with https://github.com/orgs/hackforla/projects/67. The old URL is a classic project board, which GitHub retired, and now returns 404. Project 67 is "HfLA: Open Roles" and already holds the DevOps CoP's open-role cards.
On line 23, fill in the empty link in - [ ] [Onboard]() the selected new lead. Confirm the intended target before editing — it was never recorded. The likely answer is the onboard template, https://github.com/hackforla/devops/issues/new?template=onboard-ops-cop-lead.md, since that is the only onboarding template in the repo, but check with a CoP lead rather than assuming.
Line 3, the about: key — change Use this checklist when recruiting a new Devops CoP Lead to DevOps.
Line 4, the title: key — change Recruit new Devops CoP lead to Recruit new DevOps CoP lead. Worth a moment's thought rather than a blind find-and-replace: this key sets the title of every issue the template generates from now on, so it is a behaviour change rather than prose. Existing issues keep their titles and are not in scope.
Line 17 — change the link text [#Devops Slack] to [#ops Slack]. This is not a casing fix.CV7QGL66B is the #ops channel, so the channel name is wrong rather than mis-cased, and #DevOps would be equally inaccurate. Every other reference to that id already says #ops — README.md, CONTRIBUTING.md and close-fork-prs.yml in this repo, the same three files in devops-security and incubator, and five pages of the wiki — leaving this line the only outlier. Leave the URL alone.
Confirm both links resolve from the rendered template, and that the pre-filled title and the Slack link text both read DevOps. GitHub renders issue templates from the default branch only, so none of this is observable from your branch — come back after the PR merges.
Resources/Instructions
File to change: recruit-new-lead.md (links on lines 15 and 23; Devops spellings on lines 3, 4 and 17)
The casing fix was folded in here on 2026-09-04 rather than filed separately, because it is the same file. Verified that day: these three are the only Devops spellings anywhere under .github/ — the other seven templates in that directory were each checked and are clean, so no follow-up sweep is needed. Note this is a casing fix, not part of the ops → devops repository rename cleanup that Finish the ops to devops rename in the CoP lead onboarding templates and the CoP: Ops label #190 covers; the file matches a search for "ops" for a different reason.
Line numbers were accurate when this issue was written and may drift. If they no longer match, find the lines by their text: "Post card on [Open Roles board]" and "Onboard the selected new lead".
Evidence the old board is gone: https://github.com/hackforla/devops/projects/1 returns HTTP 404. GitHub retired classic projects.
Evidence project 67 is the right replacement: it is public, open, and contains "CoP: DevOps: Open Role for: CoP Project Manager (PM)" — matching the title format that post-an-open-role.md generates.
Overview
We need to fix two broken links, two wrong-cased
Devopsspellings and one wrong Slack channel name in the recruit-new-lead issue template, so that whoever runs a lead recruitment isn't sent to a 404 and the issue it generates spells the team's name the way the rest of the org does. One link points at a classic project board GitHub has retired, the other has an empty target.Action Items
https://github.com/hackforla/devops/projects/1withhttps://github.com/orgs/hackforla/projects/67. The old URL is a classic project board, which GitHub retired, and now returns 404. Project 67 is "HfLA: Open Roles" and already holds the DevOps CoP's open-role cards.- [ ] [Onboard]() the selected new lead. Confirm the intended target before editing — it was never recorded. The likely answer is the onboard template,https://github.com/hackforla/devops/issues/new?template=onboard-ops-cop-lead.md, since that is the only onboarding template in the repo, but check with a CoP lead rather than assuming.about:key — changeUse this checklist when recruiting a new Devops CoP LeadtoDevOps.title:key — changeRecruit new Devops CoP leadtoRecruit new DevOps CoP lead. Worth a moment's thought rather than a blind find-and-replace: this key sets the title of every issue the template generates from now on, so it is a behaviour change rather than prose. Existing issues keep their titles and are not in scope.[#Devops Slack]to[#ops Slack]. This is not a casing fix.CV7QGL66Bis the#opschannel, so the channel name is wrong rather than mis-cased, and#DevOpswould be equally inaccurate. Every other reference to that id already says#ops—README.md,CONTRIBUTING.mdandclose-fork-prs.ymlin this repo, the same three files indevops-securityandincubator, and five pages of the wiki — leaving this line the only outlier. Leave the URL alone.DevOps. GitHub renders issue templates from the default branch only, so none of this is observable from your branch — come back after the PR merges.Resources/Instructions
Devopsspellings on lines 3, 4 and 17)onboard-devops-cop-lead.md, which tells every incoming CoP lead to join#devops. Out of scope here; fixed separately in Name the Slack channel #ops in the CoP lead onboard template #217.Devopsspellings anywhere under.github/— the other seven templates in that directory were each checked and are clean, so no follow-up sweep is needed. Note this is a casing fix, not part of theops→devopsrepository rename cleanup that Finish the ops to devops rename in the CoP lead onboarding templates and the CoP: Ops label #190 covers; the file matches a search for "ops" for a different reason.https://github.com/hackforla/devops/projects/1returns HTTP 404. GitHub retired classic projects.post-an-open-role.mdgenerates.onboard-ops-cop-lead.md. If the pendingops→devopsrename cleanup (see Change ops repository name to 'devops' #155, Update info in ops repo for devops rename #156, Update info in ops wiki for devops rename #157) renames that file, this link must be updated at the same time.