Repository navigation
Let scraper admins move a scraper to another repository - #1553
Closed
benrfairless wants to merge 1 commit into
Closed
benrfairless wants to merge 1 commit into
benrfairless wants to merge 1 commit into
Conversation
benrfairless
added this pull request to stack #1550
September 16, 2026 08:12
benrfairless
force-pushed
the
feature/1546-change-repository
branch
from
September 16, 2026 08:20
7d6fa42 to
2a80518
Compare
A Change repository panel in the scraper's Danger Zone re-points the scraper at a repository on any forge the current user and the scraper's owner are both on, keeping the scraper's address on morph.io, its data, its runs, its watchers and its collaborators. The local clone is thrown away and fetched afresh; any project deploy token the old repository had goes with it. ChangeRepositoryService refuses a repository the user cannot see, or one that belongs to a different account on the new forge than the scraper's Owner holds there, so a scraper cannot quietly change hands. This is the operation that linking identities exists to enable (ADR 0008): moving OAF's scrapers from GitHub to GitLab without breaking the data URLs embedded in other people's code. Assisted-by: Claude Code:anthropic.claude-fable-5-1
benrfairless
force-pushed
the
feature/1546-change-repository
branch
from
September 16, 2026 08:26
2a80518 to
0942dd0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #1546. Sixth layer of the stack, on #1552. This is the operation that linking identities exists to enable (ADR 0008): moving OAF's scrapers from GitHub to GitLab without breaking the data URLs embedded in other people's code and READMEs.
What
A Change repository panel in the scraper's Danger Zone re-points the scraper at a repository on any forge the current user and the scraper's Owner are both on. It keeps the scraper's address on morph.io, its data, its runs, its watchers and its collaborators. The local clone is thrown away and fetched afresh from the new repository through the usual
CreateFromForgeWorker; any project deploy token the old repository had goes with it, and a stale-permissions flag is cleared.ChangeRepositoryServicerefuses a repository the user cannot see, and one that belongs to a different account on the new forge than the scraper's Owner holds there, so a scraper cannot quietly change hands. If the repository has a different name on the new forge the scraper takes that name, so/:owner/:namestays truthful.Gated on
:destroy(scraper admin), the same as the other Danger Zone actions.Verified
spec/controllers/scrapers_controller_change_repository_spec.rb: the move (attributes, runs kept, clone cleared, sync queued), refusal for a repository under another account, refusal for one that cannot be seen, and a bystander getting the usual 404.spec/services/change_repository_service_spec.rb: renamed repositories, deploy token cleanup, and the not-connected message.make quick-testsgreen (990 examples, coverage 81.77%),rubocopandhaml-lintclean.Notes for review
The panel offers one form per other forge the user could move to, pre-filled with
<owner login on that forge>/<scraper name>, since that is the overwhelmingly common case for a migration.Assisted-by: Claude Code:anthropic.claude-fable-5-1