ci: stop the mirror workflow from cross-referencing upstream PRs - #11
Merged
Conversation
The mirror workflow wrote each fork PR body with the raw upstream PR URL as plain text. GitHub parses a bare issue/PR URL and posts a cross-referenced timeline event on the upstream PR, notifying the upstream maintainer on every mirrored PR. Wrap the URL in an inline-code span so GitHub no longer links it or emits a cross-reference, while keeping it readable and copyable.
andrii-solokh
had a problem deploying
to
Base Scratch Org
June 23, 2026 09:04 — with 
GitHub Actions
Failure
GitHub Actions
Failure
…g upstream
The overlay commit subject embedded `#${n}`. In a fork, GitHub resolves a `#N` that does not exist locally against the parent repo, so every force-pushed overlay commit posted a 'pushed a commit that referenced this pull request' event on the upstream PR. Drop the `#` (use `upstream-pr-${n}`, matching the branch name) so the subject no longer autolinks.
andrii-solokh
changed the title
andrii-solokh
had a problem deploying
to
Base Scratch Org
June 23, 2026 09:08 — with
GitHub Actions
Failure
GitHub Actions
Failure
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.
Stops the
Mirror Upstream PRsworkflow from posting cross-reference events on upstream (jongpie/NebulaLogger) PRs. The upstream maintainer was getting tagged on every mirrored PR. There were two distinct sources.Before
1. Mirror PR body —
mentioned this pull requestThe body embedded the upstream PR URL as plain text:
GitHub autolinks a bare issue/PR URL and posts a
mentionedevent on the upstream PR (once per mirror).2. Overlay commit subject —
pushed a commit that referenced this pull request(the flood)The CI-overlay commit subject embedded
#${n}:In a fork, GitHub resolves a
#Nthat does not exist locally against the parent repo (renders asjongpie#995). Every force-pushed overlay commit (new SHA per re-mirror) posted apushed a commit that referenced this pull requestevent on the upstream PR. This is the bulk of the noise.After
1. URL wrapped in an inline-code span — GitHub does not link or cross-reference URLs inside code spans:
2.
#dropped from the overlay commit subject (now matches the branch name) — no autolink, no cross-reference:Both stay readable; neither emits a timeline event upstream.
Note: this stops all future cross-references. The events already posted on upstream PRs are permanent GitHub timeline entries and cannot be removed by us or the maintainer.