Skip to content

FY26Q2 Stage Lead planning issue: Create

Issue description

This issue outlines the themes that will be the focus of the devopscreate stage lead during Q2 of FY26.

Issue board: https://gitlab.com/groups/gitlab-org/-/boards/1538653

Themes

Expand on complex topics

Issue Group(s) Status Effort Priority Details
Docs spike: Branch rules, protected branches, c... (gitlab-org/gitlab#556935) devopscreate In progress High High Brendan is using this issue to scope out the needed work.
Docs: Git, expand info on complex branching flows (gitlab-org/gitlab#536484) devopscreate Waiting for Amy medium high Target milestone is 17.x. Led by: Amy
Docs: research, document various merge methods ... (gitlab-org/gitlab#546033) groupsource code Waiting for Amy high/massive medium/high Target milestone is %18.2. Led by: Amy
Rebases: reunite existing UI info, create new page (gitlab-org/gitlab#521069 - closed) groupcode review Complete medium medium Done in %18.0. Led by: Amy
Docs: track improvements to monorepo pages (gitlab-org/gitlab#545149 - closed) groupgitaly in progress high medium Discovered the pages in %18.1. Target is %18.1. Cleanup done, MRs over to Gitaly managers for final review
https://gitlab.com/gitlab-org/gitlab/-/issues/546225+ groupgitaly blocked on gitlab-org/gitlab#545149 (closed) unknown unknown Got more info from PS. Needs review by Amy to determine how to succeed.

Process and tooling improvements

  • Short description: address process gaps that were identified as problems in Q1, advocate for engineering fix for tooling gap that caused user-facing problems
  • Reasoning: The editor-extensions repositories are external, and each needs a custom CI/CD job to verify external links to docs.gitlab.com are valid. The process gap was identified as a blocker for contributions from the solutions architect teams
  • Note:
Issue Group(s) Status Effort Priority Details
[VS Code] Add automated checking of external li... (gitlab-org/gitlab-vscode-extension#1934) groupeditor extensions Advocated, awaiting eng assignment unknown medium Target: 18.x. Led by: Technical Writer (TW name) or Engineer
Add "lychee" tool to check internal links (and ... (gitlab-org/cli#7848 - closed) groupcode review Advocated, awaiting eng assignment low medium Target milestone is 17.x. Led by: Amy
Add a "docs feedback or ideas" section to TW page (gitlab-com/content-sites/handbook!13093 - closed) Solutions Architects Technical Writing Leadership medium low Target milestone: %18.1

Miscellaneous

  • Short description: Captures unexpected opportunities that come my way
  • Reasoning:
Issue Group(s) Status Effort Priority Details
https://gitlab.com/gitlab-org/ux-research/-/issues/3486+ devopscreate Waiting for Amy to review for Create topics Low, Medium, High Low, Medium, High Target milestone is 17.x. Led by: Technical Writer (TW name) or Engineer
Create docs: clean up bolding (gitlab-org/gitlab#537730 - closed) devopscreate In spare moments low low Make translation team's work easier

GitLab Duo re-tiering

I recognized that https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1300+ required immediate work with the Editor Extensions repos to fix error messaging and UI text after the re-tiering.

Issue Group(s) Status Effort Priority Details
Review GitLab Duo entitlement statements in the... (#1331 - closed) groupeditor extensions in progress high urgent tracks overall work of getting the extensions themselves updated. Docs were already done as part of Jon's work for devopsai-powered.
Update how to access Duo in XML files (gitlab-org/editor-extensions/gitlab-jetbrains-plugin#986 - closed) groupeditor extensions in progress medium, collaborative urgent Update marketplace listing of JetBrains and other extensions. This information is not stored in the Git repositories for the extensions, and requires the PM's assistance.
Update VS Code Duo Pro entitlements outside of ... (gitlab-org/gitlab-vscode-extension#1976 - closed) groupeditor extensions in progress unknown, collaborative urgent tracks UI fixes specific to the VS Code extension, in files whose ramifications I do not understand

Legend:

  • ⏳ : Waiting for <...>. technical writer, or PM input, or Engineering input
  • 🚧 : In progress
  • ✅ : Complete
  • 🏋🏽 : Stretch goal (add next to any item that is aspirational this quarter)

Ongoing tasks

Manage TW-DRI assignments for all milestones:

Specific TW milestone planning issues:

  • X.Y. Release date: YYYY-MM-DD
  • X.Y. Release date: YYYY-MM-DD
  • X.Y. Release date: YYYY-MM-DD

References

Retrospective

After the quarter is complete, create discussion threads with the following titles. Use these discussion threads for self-reflection and to note feedback from others about how the quarter went.

## 👍 What went well?
## 👎 What didn't go as well?
## 📈 What could be improved for next time?
Edited by Amy Qualls