Skip to content

Commit

Permalink
Remove reference to TL opening PR for govuk-user-reviewer
Browse files Browse the repository at this point in the history
This actually isn't something we want to encourage, as it's only
useful if the TL follows all the leavers ticket steps. If they
only update govuk-user-reviewer, they may actually mask the fact
that this was a technical employee, and we may miss the other
steps (like removing AWS account).
  • Loading branch information
ChrisBAshton committed Feb 13, 2024
1 parent f5986b8 commit f5b87fc
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions source/manual/tech-lead-responsibilities.html.md
Expand Up @@ -34,10 +34,9 @@ If the developer is new to GOV.UK, then it’s worth taking them through the [ov

## Managing leavers

When a team member leaves GOV.UK, the tech lead should raise a PR in the GOV.UK [user reviewer][] ([sample pr][]) and ensure their team's Delivery Manager has informed Business Operations of the leaver/mover.
When a team member leaves GOV.UK, the team's Delivery Manager should inform Business Operations of the leaver/mover.

[user reviewer]: https://github.com/alphagov/govuk-user-reviewer
[sample pr]: https://github.com/alphagov/govuk-user-reviewer/pull/542
This eventually leads to a ticket in the [JML view](https://govuk.zendesk.com/agent/filters/63966232) Zendesk group, which Senior Tech will process.

## Being aware of the health of your team

Expand Down

0 comments on commit f5b87fc

Please sign in to comment.