Skip to content

chore: redirect new issues to amule-org/amule + soft-nudge PRs - #915

Merged
mrjimenez merged 1 commit into
amule-project:masterfrom
got3nks:chore/redirect-issues-to-new-repo
Jun 7, 2026
Merged

chore: redirect new issues to amule-org/amule + soft-nudge PRs#915
mrjimenez merged 1 commit into
amule-project:masterfrom
got3nks:chore/redirect-issues-to-new-repo

Conversation

@got3nks

@got3nks got3nks commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Users still file issues and PRs on this repository via SEO and old bookmarks. Add a layered redirect calibrated by how disruptive each needs to be:

  1. .github/ISSUE_TEMPLATE/config.yml — disables blank issues and surfaces a single contact link to amule-org/amule in the "New issue" UI. Hard redirect.
  2. .github/workflows/redirect-issues.yml — backstop for users who reach /issues/new directly. Posts a redirect comment, closes as not_planned, locks.
  3. .github/pull_request_template.md — soft nudge only. Prefills the PR description with a "this repo is a mirror" note. Doesn't block; maintainers can still open PRs here when needed (mirror syncs, hotfixes).

Out of scope

  • Existing open issues / PRs are NOT touched.
  • The workflow only fires on issues: opened. PRs are never auto-closed — only their description is prefilled with the nudge.

Issue tracking has moved to amule-org/amule. Users still file
issues and pull requests on this (legacy mirror) repo via SEO
and old bookmarks. Add three layers, calibrated by how
disruptive the redirect needs to be:

(1) .github/ISSUE_TEMPLATE/config.yml — disables blank issues
    and replaces the "New issue" UI with a single contact link
    pointing at the new repository. Hard redirect — users
    can't bypass it from the UI.

(2) .github/workflows/redirect-issues.yml — backstop for the
    few users who reach /issues/new directly: auto-comments
    with the new-home pointer, closes as not_planned, and
    locks the thread.

(3) .github/pull_request_template.md — soft nudge. The "New
    pull request" UI prefills the description with a "this
    repo is a mirror, file at amule-org/amule" note. Doesn't
    block anything; maintainers can still open PRs here when
    needed (e.g. mirror syncs, emergency hotfixes).

Existing open issues and PRs are NOT touched.
@got3nks
got3nks force-pushed the chore/redirect-issues-to-new-repo branch from ed81aab to 92f7254 Compare June 7, 2026 20:01
@got3nks got3nks changed the title chore: redirect new issues to amule-org/amule chore: redirect new issues to amule-org/amule + soft-nudge PRs Jun 7, 2026
@mrjimenez
mrjimenez merged commit 1dea568 into amule-project:master Jun 7, 2026
7 checks passed
mrjimenez pushed a commit that referenced this pull request Jun 8, 2026
Re-introduces the two static GitHub-UI redirects that #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 #915 / commit 1dea568 state.

This PR exists in draft as the follow-up #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).
@got3nks
got3nks deleted the chore/redirect-issues-to-new-repo branch June 8, 2026 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants