Overview
We need to finish the ops → devops rename inside this repo's own issue templates and label list, which the 2024 repo rename left behind. Two template files still have ops in their filenames and "Ops" throughout their names and body text, and the CoP: Ops label still exists — so the CoP's onboarding and offboarding checklists advertise a community that no longer goes by that name.
Action Items
Scope was checked before writing this — three things that look in scope are not. #155 is the repository rename and is already done (gh api repos/hackforla/devops --jq .full_name returns hackforla/devops); #157 is the wiki pages and every box on it is ticked; #156 is closed. None of them touches .github/ISSUE_TEMPLATE/. recruit-new-lead.md also matches a search for "ops", but those hits are Devops vs DevOps casing, which is a different problem, and its broken project-board link is already #170.
1. Rename the two template files
Verified 2026-08-26: nothing in devops, devops-security, incubator, devops.wiki or incubator.wiki references either filename, so no inbound link breaks. The picker lists templates by their name: field rather than filename, so the rename is invisible to contributors — it is for whoever reads the directory.
2. Fix the template names and body text
onboard-ops-cop-lead.md (line numbers accurate when written; find each by its surrounding text):
offboard-ops-cop-lead.md:
3. Rename the CoP: Ops label
Use the API rename rather than delete-and-recreate: it preserves the label id, so both issues carrying it keep it (2 issues, 1 open, as of 2026-08-26). Note this is a direct API change with no PR trail, so record it in the ticket. Pre-change state, to reverse it: name CoP: Ops, color C2E0C6, empty description.
4. Verify after the PR merges
The template picker renders from the default branch only, so none of section 1 or 2 is observable from a branch.
Resources/Instructions
Out of scope, deliberately: recruit-new-lead.md's Devops → DevOps casing (a separate inconsistency, and that file already has #170 open against it), the wider Devops/DevOps casing sweep across the org, and renaming the Google Drive folder or 1Password vault themselves.
Google Drive and 1Password are both deferred (2026-09-06). Four lines name those two external systems, and this ticket leaves all four exactly as they are:
Add to Ops drive as Manager — onboard, line 25Ops vault — onboard, line 34Demote to 'Contributor' on Ops Google drive — offboard, line 17Ops vault — offboard, line 22
"Ops drive" and "Ops vault" are the names of a real Google Drive folder and a real 1Password vault, not prose. Renaming them in the template would assert that those systems were renamed too, and if they were not, the checklist sends a new lead looking for something that does not exist — worse than the stale name. Neither string appears anywhere else in the three repos or either wiki, so the repos cannot settle it. So this ticket does not ask anyone to check, and does not change them. Do not treat them as a missed rename; a follow-up can pick them up once the Drive and vault sides are settled — the vault part overlaps #164/#165, which are already about 1Password vault cleanup.
Also out of scope, and worth knowing before you run the rename in section 3: hackforla/knowledgebase-content has its own CoP: Ops label (BFDADC), which is a different label from this repo's (C2E0C6) — it is one row of an org-wide CoP taxonomy alongside CoP: Product, CoP: Engineering, CoP: Design, CoP: Data Science and others. Renaming this repo's label does not touch it, and #132's action item "Add the label: CoP: Ops" points at that repo rather than this one, so nothing there breaks. But once this ticket lands, the same community of practice is named CoP: DevOps here and CoP: Ops there. Do not rename the knowledgebase-content label as part of this ticket — changing one row of a taxonomy shared by every CoP in the org belongs to whoever owns that repo and board 40 (P: Guides: Knowledgebase Content Tracker), not to us. Raise it with them if you think it should follow.
Overview
We need to finish the
ops→devopsrename inside this repo's own issue templates and label list, which the 2024 repo rename left behind. Two template files still haveopsin their filenames and "Ops" throughout their names and body text, and theCoP: Opslabel still exists — so the CoP's onboarding and offboarding checklists advertise a community that no longer goes by that name.Action Items
Scope was checked before writing this — three things that look in scope are not. #155 is the repository rename and is already done (
gh api repos/hackforla/devops --jq .full_namereturnshackforla/devops); #157 is the wiki pages and every box on it is ticked; #156 is closed. None of them touches.github/ISSUE_TEMPLATE/.recruit-new-lead.mdalso matches a search for "ops", but those hits areDevopsvsDevOpscasing, which is a different problem, and its broken project-board link is already #170.1. Rename the two template files
git mv .github/ISSUE_TEMPLATE/onboard-ops-cop-lead.md .github/ISSUE_TEMPLATE/onboard-devops-cop-lead.mdgit mv .github/ISSUE_TEMPLATE/offboard-ops-cop-lead.md .github/ISSUE_TEMPLATE/offboard-devops-cop-lead.mdVerified 2026-08-26: nothing in
devops,devops-security,incubator,devops.wikiorincubator.wikireferences either filename, so no inbound link breaks. The picker lists templates by theirname:field rather than filename, so the rename is invisible to contributors — it is for whoever reads the directory.2. Fix the template names and body text
onboard-ops-cop-lead.md(line numbers accurate when written; find each by its surrounding text):name: Onboard Ops CoP Lead→Onboard DevOps CoP LeadOps meeting→DevOps meetingoffboard-ops-cop-lead.md:name: Offboard Ops CoP Lead→Offboard DevOps CoP Leadremove [NEW LEAD NAME] from the Ops CoP leads team→DevOps CoP leads team3. Rename the
CoP: Opslabelgh api -X PATCH 'repos/hackforla/devops/labels/CoP%3A%20Ops' -f new_name='CoP: DevOps'Use the API rename rather than delete-and-recreate: it preserves the label id, so both issues carrying it keep it (2 issues, 1 open, as of 2026-08-26). Note this is a direct API change with no PR trail, so record it in the ticket. Pre-change state, to reverse it: name
CoP: Ops, colorC2E0C6, empty description.4. Verify after the PR merges
The template picker renders from the default branch only, so none of section 1 or 2 is observable from a branch.
Ops vaultlines, which this ticket leaves untouchedResources/Instructions
74a37e5Complexity: Small→complexity: smallrename, 2026-08-24, and its template follow-up Match renamed complexity: small label in open-role template #184hackforla/opsURLs all still redirect and work, so nothing here is broken for a reader — this is clarity, not an outage. Prioritize accordinglyOut of scope, deliberately:
recruit-new-lead.md'sDevops→DevOpscasing (a separate inconsistency, and that file already has #170 open against it), the widerDevops/DevOpscasing sweep across the org, and renaming the Google Drive folder or 1Password vault themselves.Google Drive and 1Password are both deferred (2026-09-06). Four lines name those two external systems, and this ticket leaves all four exactly as they are:
Add to Ops drive as Manager— onboard, line 25Ops vault— onboard, line 34Demote to 'Contributor' on Ops Google drive— offboard, line 17Ops vault— offboard, line 22"Ops drive" and "Ops vault" are the names of a real Google Drive folder and a real 1Password vault, not prose. Renaming them in the template would assert that those systems were renamed too, and if they were not, the checklist sends a new lead looking for something that does not exist — worse than the stale name. Neither string appears anywhere else in the three repos or either wiki, so the repos cannot settle it. So this ticket does not ask anyone to check, and does not change them. Do not treat them as a missed rename; a follow-up can pick them up once the Drive and vault sides are settled — the vault part overlaps #164/#165, which are already about 1Password vault cleanup.
Also out of scope, and worth knowing before you run the rename in section 3:
hackforla/knowledgebase-contenthas its ownCoP: Opslabel (BFDADC), which is a different label from this repo's (C2E0C6) — it is one row of an org-wide CoP taxonomy alongsideCoP: Product,CoP: Engineering,CoP: Design,CoP: Data Scienceand others. Renaming this repo's label does not touch it, and #132's action item "Add the label:CoP: Ops" points at that repo rather than this one, so nothing there breaks. But once this ticket lands, the same community of practice is namedCoP: DevOpshere andCoP: Opsthere. Do not rename the knowledgebase-content label as part of this ticket — changing one row of a taxonomy shared by every CoP in the org belongs to whoever owns that repo and board 40 (P: Guides: Knowledgebase Content Tracker), not to us. Raise it with them if you think it should follow.