Repository navigation
Upstream being spammed by fork using this app #466
Description
Hi there,
Whenever a commit is made in an upstream repo, a fork that is using this app ends up spamming us because of failed CI runs.
Example spammy notifications:
Example failed CI run causing the spam: https://github.com/https-quantumblockchainai-atlassian-net/fastify/actions/runs/2839917467
The offending PR in the fork: https-quantumblockchainai-atlassian-net/fastify#2
Please can this be investigated?
Reacted by Brian Smith
Reacted by Manuel Spigolon, Nobuyoshi Nakada and Brian Smith
Activity
Fdawgs commentedon Aug 31, 2022
@wei
wei commentedon Aug 31, 2022
Hi @Fdawgs thanks for opening the issue. Pull app automates the creation of prs but does not request or have permission to manage the workflow runs. I recommend revising workflow files, disabling notifications for the affected repo, or correspond with GitHub support directly regarding your concern/feedback regarding this behavior~
mame commentedon Oct 24, 2022
FYI, I am experiencing the same issue (upstream: https://github.com/ruby/ruby, fork: https://github.com/turkdevops/ruby). This is really annoying. I have filed a question of this behavior in https://github.com/orgs/community/discussions/37095
bsmth commentedon Feb 17, 2023
I'm just adding a
+1that MDN maintainers are experiencing this also on many forks of https://github.com/mdn/content. @wei would you consider adding some functionality to your bot that closes stale PRs by default as most of these are inactive, e.g.:We've already limited offending workflows not to run on forks, but of course this has to be syncd into a fork's
main.Thank you :)