Repository navigation
chore(ci): repoint push-email-notify to smtp-notify-action #62
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: hyperpolymath/network-ambulance
Length of output: 5176
🌐 Web query:
GitHub Actions workflow syntax push branches branch deletion event payload head_commit null github.event.deleted💡 Result:
In GitHub Actions, deleting a branch is technically handled as a push event [1][2]. When you delete a branch, GitHub triggers a push event to the repository with the
deletedattribute in the webhook payload set totrue[1]. Because this is a push event, it can inadvertently trigger workflows configured withon: push[2]. Within this specific event, thehead_commitobject in the GitHub Actions payload will benullbecause there is no commit associated with the deletion of a ref [1]. To prevent your workflows from running or failing when a branch is deleted, you should add a conditional check to your jobs using thegithub.event.deletedproperty [3][4][5][6]. Recommended Implementation: You can skip jobs when a branch is deleted by adding the following condition to your workflow YAML [3][6]: jobs: your_job_name: if: ${{!github.event.deleted }} runs-on: ubuntu-latest steps: - name: Your step run: echo "This will not run on branch deletion." Key Technical Details: - Push Event Payload: Thepushevent includes adeletedboolean field [1]. When a branch is deleted, this field istrue[1]. - head_commit: In the context of a branch deletion push event,github.event.head_commitisnull[1]. - Distinguishing Events: If you need to specifically handle branch deletions as a primary trigger rather than filtering them out, consider using thedeleteevent instead ofpush, which provides distinct payload information such asrefandref_type(e.g., branch or tag) [1][7][2].Citations:
Exclude branch deletions from the notification job.
branches: ['**']does not exclude branch-deletionpushevents. These events havegithub.event.deleted == trueandhead_commit == null, so the job can send an email with an empty head message. Addgithub.event.deleted != trueto the job condition.🤖 Prompt for AI Agents
Source: MCP tools