Post-migration cleanup: finish what the rename left behind

[splaisan]

A rename is not finished when the rename succeeds. GitHub's redirect keeps every leftover working, so nothing fails and no check turns red — which is exactly why the leftovers survive. This ticket lists what is left in Nucleomics-VIB/mplotter, measured on 2026-09-03, and it is worked in this repo's own session.

The rule this comes from, with the detection commands and the reasoning: Nucleomics-VIB/SP_AI_skills -> studies/github_repo_renaming/post_migration_rule.md. Umbrella ticket for the branch half: Nucleomics-VIB/SP_AI_skills#64.

What applies here

item	applies	measured
Default branch is master	yes	master
GitHub Pages builds from master	YES	source.branch = master
/master/ URLs to relink	no	0 into this repo, 0 elsewhere
Repo was renamed	no	name unchanged
Old name in a URL	no	0 line(s)
Old name in docs	no	0 line(s)
Old name in build/deploy files	no	0 line(s)
Old name in code/scripts	no	0 line(s)
Old name in history files	no	0 line(s)
Branch protection	MISSING	no ruleset — see #63
Self-hosted runner	no	-
Stale local checkout	none found	0 outside /opt/github/

Read this first — specific to this repo

Only archive row in the programme, and it serves a LIVE Pages site. Settle the archive decision first — an archived repo is read-only and cannot be renamed.

⚠️ Pages builds from master, and the site is live

repos/Nucleomics-VIB/mplotter/pages reports source.branch = master, and the site is https://nucleomics-vib.github.io/mplotter/ . A Pages source names a literal branch. A broken Pages build is not a failing check — the site simply goes stale or 404s.

Record the source before, re-read it after, set source.branch yourself if GitHub did not move it, then load the site and confirm 200.

The pass, in order

• Re-run the detection block from post_migration_rule.md — the numbers above are one point in time.
• Record the Pages source: gh api repos/Nucleomics-VIB/mplotter/pages
• Rename the branch: gh api -X POST repos/Nucleomics-VIB/mplotter/branches/master/rename -f new_name=main
• Re-read gh api repos/Nucleomics-VIB/mplotter/pages, confirm source.branch is main, set it if GitHub did not, then load the site and confirm 200.
• Fetch every URL you changed: curl -s -o /dev/null -w '%{http_code}' -L <url> must print 200.
• This repo has no ruleset — master/main can be force-pushed or deleted by anyone with write access. That is #63, not this ticket, but a migration session is the cheapest moment to close it.
• Close this ticket quoting the verified 200s.

Not urgent

Nothing here is broken today. Every old URL answers through the redirect and no check is red. That is precisely the risk: this decays quietly, and it is cheapest to fix while the rename is fresh.