-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce notifications from Greetings
workflow
#2286
Comments
I vote for Option 3 since we are not inundated with an extremely large number of new contributors. |
Are those Github notifications? Where do I see them? |
@cosenal Whenever I create an issue, I get these Github notifications. Each notification in the screenshot is due to adding a label, assigning it to myself, or when editing the issue description. There's no way to reduce these based on what I found. https://github.com/unitaryfund/mitiq/actions/workflows/greeting.yml Edit: You can see these when @Misty-W created the PT issue. If I had created the issue, I would have gotten all of these notifications. The |
The You can see it in action at #2208 (comment) when a person is new to the repo. |
@purva-thakre I think this is something to do with your personal GitHub notifications. I have never received any of these notifications. I wasn't able to find anything on first glance that would apply here, but I didn't do a thorough search through the notifications documentation: https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications. I would think you can to turn off these notifications given others are not receiving them (or set up a filter in your email). |
The
.github/workflows/greeting.yml
workflow sends too many notifications for someone who is not a first-time contributor.Option 1: Make changes to the workflow to work around
actions/first-interaction@v1
as the issue related to notifications is known to the maintainers and has not yet been fixed. actions/first-interaction#15Option 2: Use an alternative to
actions/first-interaction@v1
from the Github Marketplace.Option 3: Remove the workflow and rely on one of the maintainers to comment with the message.
The text was updated successfully, but these errors were encountered: