Repository navigation
[accordwimsy] Releases, and a repository made again by the Forgejo's migration with GitHub's authors - #50
Merged
Conversation
…ir files checked against GitHub's SHA-256 Signed-off-by: AO55 <AO55@reden-emu.dev>
…ch keeps GitHub's authors, and adopt its copy Signed-off-by: AO55 <AO55@reden-emu.dev>
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
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.
Phase 1 of the GitHub to git.scarletnx.dev bridge: the releases come over, and a repository can be made again by the Forgejo's own migration, the one way its issues, pull requests and comments carry their GitHub authors. Phase 2, the way back, is separate.
Releases (
ACCORDWIMSY_RELEASES)repository:tag pattern[:newest], at most 16. A word that is no rule stops the program, and the error names the word. Production will setnightly:nightly-*:3 edenprobe:*.release.partand checked against GitHub's size and SHA-256 (digest) before sending:libssl-dev.ACCORDWIMSY_GRACE_DAYS, as a branch does.state.jsontakes the releases back by tag and the files back by size, with nothing fetched again.accordwimsy migrate REPOSITORYandaccordwimsy adopt REPOSITORYmigrate:<name>-bot-<stamp>, archived and private;POST /repos/migratewithGITHUB_TOKEN(issues, PRs, comments, labels and milestones; no releases, no wiki);A repository that a migration already made is refused.
adoptrebuilds the repository'sstate.jsonentry from the migration's copy:updated_at. GitHub's value for each issue, so the next pass reads everything once and writes only what changed.updateGitForPullRequest):<owner>/<branch>. It now moves with GitHub's commits, stays out of the grace (otherwise it would be deleted after 7 days, and Forgejo would close the PR), and is deleted on close;It refuses and writes nothing when:
Checks
make testinaccordwimsy/, Linux: 224 of 224.adoptreads.gone, and comments matched in the wrong order when GitHub lists them by update time.test-mutants.py50/50,test-install.sh,check-docs.py.Not checked yet:
post-buildruns these tests there.adopt's refusals guard the state if it differs.