Silence github actions notifications #1
Closed
Conversation
This file contains 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
basepi
force-pushed
the
fixupmariocandela
branch
from
70ebd44 to
cc93a0b
Compare
basepi
force-pushed
the
fixupmariocandela
branch
from
cc93a0b to
3c6daec
Compare
|
Finally figured it out, I was able to set your fork to "ignore" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ever since your PR against the Elastic APM agent for Python, Github actions has been trying (and failing) to run all of our upstream workflows on your repo. This has resulted in a huge volume of "failed workflow" notifications in my inbox.
Could you disable github actions on your fork? I think the setting should be here: https://github.com/mariocandela/apm-agent-python/settings/actions
Or, you can merge this PR, which would also disable all the github actions.
Thank you!
(For reference, this happened because you opened your PR from your
mainbranch instead of creating a branch dedicated to your PR. Good note for next time. Thanks again for the contribution!)