Prevent forks from polluting issues

[fsc-eriker]

Every time the workflow runs it gets noted in Github on the bugs it links to. While this could marginally be tolerated or even construed as useful, it gets completely ridiculous when forks of the project add the same comment at the same time. See for example anthropics/claude-code#63686

[luojunyuan]

Please report this repository to GitHub for CI abuse.

[alexisLefebvre]

Please report this repository to GitHub for CI abuse.

Which one? Main and/or forks? How would that prevent the issue in the future?

[cpt-sd76vg]

I think the current design of automatically creating issues that contain auto-linked PR/issue references is problematic in itself.

If this project is going to post reports as GitHub issues, it should at least avoid generating automatic PR/issue backlinks. If links are really necessary, GitHub officially documents redirect.github.com as a way to avoid creating backlinks, so external GitHub Issue/PR URLs in these reports should at minimum be rewritten to use that.

Otherwise, the generated reports end up polluting the timelines of unrelated repositories through automatic backlinks.

[tredondo]

the generated reports end up polluting the timelines of unrelated repositories through automatic backlinks.

That's how I discovered this project.

[alexisLefebvre]

See this related PR:

• Avoid upstream GitHub cross-reference notifications in digest issues #274

[yuriever]

You can just write a script to block it yourself. Can't you do that?