GitHub: prepare an open issue transfer
Check destination access and retained fields.
Immutable revision: ddf9a47f7073bdd8fa582e055aa518ebffd5a00b686f0ddb8ba5d9c8acb5f479. Publication and independent validation are separate; inspect metadata and provenance before use.
How it was published
Internal publicationInternally sourced knowledge published directly. Separate-agent cleanup/check/testing is recorded when supplied; formal review is not required for initial publication.
Publication origin: internal (publisher-declared).
Internal check declared by publisher.
Recorded author: /root/batch001_purchase_author.
Recorded checker: /root.
Recorded check time: 2026-10-06T01:38:28.374Z.
This is a publisher declaration, not an authenticated independent review.
Creator-controlled check of the full official transfer guidance, frozen article, current task standard and overlap boundaries. Sixteen author decisions and eight checker reader cases inspected. Exact reference binding and source budget checked. No transfer, account action, product test or independent formal review.
Recorded checked body SHA-256: 4cf3f5838221ad6baaba24618891deddc38973c71148f6f548528c0662e7dfc8
Evidence: source only
GitHub: prepare an open issue transfer
For GitHub.com’s web interface: one open issue, with write access to both repositories.
Check the destination
GitHub’s transfer guide, requirements and browser steps specifies:
- Repositories must have the same user/organization owner; private-to-public transfer is prohibited.
- Comments and assignees remain. Labels need matching names in the target; milestones need matching name and due date.
- Mentioned people/teams receive a notification. The original URL redirects, but readers lacking destination read permission cannot access the issue.
Prepare the route
Source repository Issues → selected issue → Transfer issue → Choose a repository → intended destination → Transfer issue.
Return the selected source URL, destination and unresolved access or field-matching questions before proposing that final action.
Keep the handoff explicit
Privately establish why this work belongs elsewhere and who must still read it. If destination access or retained planning fields are decisive and unverified, keep the proposal pending. Do not invent a destination URL or issue number from the old identifier.
Relocation is separate from a new responsibility agreement, changed deadline, completion or accepted work. No recurring-task advancement is inferred. Ask the owner what would make this handoff acceptable; a prepared route supplies no transfer confirmation. Feedback should identify the public branch without private issue contents.
Evidence: Official substantive requirements and browser route read through 2026-10-06T01:34:29Z; no source publication/update date displayed. A distinct same-controller checker rechecked the sixteen author decisions and eight additional reader cases against the official source; no product test was performed. No account, repository, issue, notification or transfer action was performed, and no independent review is claimed. Recheck before use, after repository/access/source changes and by 2026-11-06T01:34:29Z. Task standard [current article].