You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All solved AdGuard issues now get a "pull added a commit" spam line at the bottom caused by forks using your app. I keep clicking them accidentally expecting to see the actual commit in the original repository.
Also, if one day your account gets hacked or you decide to sell it, there will be thousands of links pointing to whatever the hacker/buyer decides to do with this page: https://github.com/apps/pull .
I've seen some previous issues in this repository, but it's still not clear to me if there's a way to stop this.
Hi @no-milestone thanks for opening the ticket. I took some time to investigate and this seems like a GitHub bug.
GitHub automatically displays a reference message in an issue when the first commit in any repository mentions that issue. This happens even if the commit comes from another fork. This message appears to be deduplicated by commit hash to prevent spam.
However, when the commit message in your repo closes the issue using the fix keyword, the original commit does not generate a similar reference message. As seen in this example, the commit only results in an issue closer message, and no "references this issue" message is added:
^ notice the same commit #.
In a world without Pull, any user syncing this commit in their forks will still cause GitHub to reference the issue. Their usernames with "references this issue" message will show up in your issues in place of Pull. Therefore, I believe this issue should be raised to the GitHub team directly as this will happen with and without Pull.
Hi. Please try in ad blocker github.com##section[aria-label="Events"] > div[class^="LayoutHelpers-module__timelineElement--"]:has(a[href="/apps/pull"])
At least you won't have to see that thing anymore)
Activity
wei commentedon Jul 30, 2025
Hi @no-milestone thanks for opening the ticket. I took some time to investigate and this seems like a GitHub bug.
GitHub automatically displays a reference message in an issue when the first commit in any repository mentions that issue. This happens even if the commit comes from another fork. This message appears to be deduplicated by commit hash to prevent spam.
However, when the commit message in your repo closes the issue using the fix keyword, the original commit does not generate a similar reference message. As seen in this example, the commit only results in an issue closer message, and no "references this issue" message is added:
^ notice the same commit #.
In a world without Pull, any user syncing this commit in their forks will still cause GitHub to reference the issue. Their usernames with "references this issue" message will show up in your issues in place of Pull. Therefore, I believe this issue should be raised to the GitHub team directly as this will happen with and without Pull.
Alex-302 commentedon Jul 31, 2025
Hi. Please try in ad blocker
github.com##section[aria-label="Events"] > div[class^="LayoutHelpers-module__timelineElement--"]:has(a[href="/apps/pull"])At least you won't have to see that thing anymore)
wei commentedon Aug 3, 2025
Closing due to inactivity. Please feel free to reply if you have any followup questions.