chore: update cron job frequency to reset github notifications #8956
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
joshua-goldstein
requested review from
mangalaman93,
meghalims,
sanjayk-github-dev,
harshil-goel,
all-seeing-code and
billprovince
as code owners
dgraph-bot
added
the
area/integrations
joshua-goldstein
changed the title
mangalaman93
approved these changes
Aug 16, 2023
sanjayk-github-dev
approved these changes
Aug 17, 2023
jbhamra1
pushed a commit
that referenced
this pull request
Aug 18, 2023
In our [scheduled runs](https://github.com/dgraph-io/dgraph/actions?query=event%3Aschedule) we see a number of "ghost" jobs. E.g. [1](https://github.com/dgraph-io/dgraph/actions/runs/5881148541). This is probably due to the following sequence of events: - github actions sends a notification to developer who created / modified cron job frequency - if this person is no longer able to receive this notification (i.e. no longer receiving emails) the action raise this ghost job with an error about unverified email This is a bug with github actions. After contacting github support they suggested changing the cron job frequency in order to reset who receives the notifications. This may solve the issue.
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.
In our scheduled runs we see a number of "ghost" jobs. E.g. 1. This is probably due to the following sequence of events:
This is a bug with github actions. After contacting github support they suggested changing the cron job frequency in order to reset who receives the notifications. This may solve the issue.