Skip to content

chore: name @RustyLegend as maintainer - #67

Merged
pushpam2404 merged 1 commit into
mainfrom
chore/codeowners
Oct 4, 2026
Merged

pushpam2404 merged 1 commit into
mainfrom
chore/codeowners

Conversation

@pushpam2404

Copy link
Copy Markdown
Member

Names a maintainer for this repository, ahead of the event.

Maintainer: @RustyLegend — the HTML and CSS site

Why both names are on every line

Code-owner review is being enforced, so one of the names on the matching line must approve before anything merges. @pushpam2404 is listed alongside the maintainer on purpose:

  • GitHub does not let anyone approve their own pull request. A line naming one person would deadlock the first time that person opened one — their own PR would be unapprovable, including by them.
  • If the maintainer is away, nothing waits. With 80 contributors landing PRs in two hours, one person being the sole approver is how a backlog forms.

What the lead keeps alone

/.github/, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md and LICENSE.

Those decide what the checks are. Without this, a pull request could change the workflow that approves it and then be approved by the workflow it just changed.

Worth knowing

This routes reviews; it does not restrict access. 30 people already have write access to all three repos through the organisation, ten of them admin. CODEOWNERS makes responsibility clear and makes GitHub request the right reviewer — it does not stop anyone else merging unless enforcement is on, which is being switched on once this lands.

Maintainer: @RustyLegend

Code-owner review is being enforced, so one of the names on the matching line
has to approve before anything merges.

@pushpam2404 is on every line on purpose. GitHub does not let anybody approve
their own pull request, so a line naming one person would deadlock the first
time that person opened one — and if the maintainer is away, nothing has to
wait for them.

Workflows, CONTRIBUTING and the licence stay owned by the lead alone, so a
pull request cannot change the checks that approve it.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congratulations on your first pull request to this repository.

Here is what happens next:

  1. The checks below need to go green. If one is red, click Details to see why — that is normal, and fixing it is part of the work
  2. A maintainer reviews within 48 hours and may leave line comments
  3. Once it is approved, a maintainer merges it

Two things that get PRs closed, so please double-check:

  • No Closes #<issue> in the description
  • The issue was never assigned to you

Nice work getting this far. Most people never open their first PR.

@pushpam2404
pushpam2404 merged commit 90cfdcf into main Oct 4, 2026
6 checks passed
@pushpam2404
pushpam2404 deleted the chore/codeowners branch October 4, 2026 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant