chore: restore mirror-redirect static config (held for post-3.0.0) - #921
Merged
mrjimenez merged 1 commit intoJun 8, 2026
Merged
Conversation
Re-introduces the two static GitHub-UI redirects that amule-project#919 removed in d8db711 to make amule-project's .github/ safe to "Sync fork" into amule-org/amule: .github/ISSUE_TEMPLATE/config.yml -- blank_issues_enabled + contact_link to amule-org .github/pull_request_template.md -- "this repo is a mirror" soft nudge prefill Both restored verbatim to their PR amule-project#915 / commit 1dea568 state. This PR exists in draft as the follow-up amule-project#919's body referenced: > After 3.0.0 ships and amule-org has its own .github/ going > forward, the two static files can be re-added to amule-project > unconditionally as full-strength mirror UX -- at that point > the repos are intentionally divergent and there's no sync > to break. See the PR description for the pre-merge checklist (3.0.0 release on amule-project, amule-org override files in place, maintainer sign-off).
|
👋 Thanks for the contribution. Heads up — this repository is a mirror. Active development happens at the project's current home: https://github.com/amule-org/amule/pulls If you re-open this pull request against amule-org/amule it will land in front of the active reviewers right away. We're leaving this PR open here too so it isn't lost — a maintainer may merge it directly from this side if it's a small fix, but the canonical place for follow-ups, review threads, and any related issues is the new repo. Sorry for the friction. |
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
2 participants
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.
Holding queue for the two static GitHub-UI redirects that #919 explicitly removed because they'd misfire on a "Sync fork" pass into
amule-org/amule(theconfig.ymlcontact link would bounce amule-org users to the page they're already on; the PR template would tell amule-org contributors "this repo is a mirror"). The follow-up note on that PR was:This PR is that follow-up, pre-staged in draft so it doesn't get lost.
Pre-merge checklist
Do not mark ready-for-review or merge until all boxes are ticked:
amule-project/amule(tag pushed, GitHub Release published).amule-org/amulehas its own.github/ISSUE_TEMPLATE/config.ymlin place (so a Sync-fork pass from this repo doesn't silently overwrite it with our "issues moved" contact link).amule-org/amulehas its own.github/pull_request_template.mdin place (same reason — the "this repo is a mirror" body would otherwise land on the active-fork side).The third condition is the one that makes the first two strictly necessary: GitHub's "Sync fork" merges new files from upstream into the fork by default. If amule-org doesn't already have its own copies of these two files when the sync hits, they propagate over and the redirect tells amule-org users to file issues at the page they're on.
What the two files do
.github/ISSUE_TEMPLATE/config.yml: setsblank_issues_enabled: falseand surfaces acontact_linktoamule-org/amule/issuesin the "New issue" picker. Hard pre-emptive nudge — most users never reach/issues/newto hit the workflow-based redirect..github/pull_request_template.md: soft pre-fill of the PR description with a "this repo is a mirror" comment. Non-blocking; maintainers can clear it and proceed.Both files are restored verbatim to their PR #915 / commit 1dea568 state. No content changes vs. what was removed in #919's d8db711.
Out of scope
The
redirect-issues.ymlandredirect-prs.ymlworkflows stay as-is on master — they're already gated bygithub.repository == 'amule-project/amule'so they're sync-safe regardless.