-
-
Notifications
You must be signed in to change notification settings - Fork 0
chore(ci): repoint push-email-notify to smtp-notify-action #101
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:
sed -n '1,140p' .github/workflows/push-email-notify.ymlRepository: hyperpolymath/vcs-ircd
Length of output: 3097
🌐 Web query:
GitHub Actions push event branch deletion github.event.deleted head_commit nullable branches filter💡 Result:
In GitHub Actions, the push event is triggered when a branch is deleted [1]. When this occurs, the workflow runs on the default branch of the repository, and the GITHUB_REF variable reflects the default branch [2][3]. Key details regarding the push event during branch deletion include: 1. head_commit is Nullable: In the webhook payload for a push event, the head_commit object can be null (e.g., when a branch is deleted) [4][5]. Workflows attempting to access fields within head_commit should account for this potential null value to avoid errors [6][7]. 2. Handling Deletion: To distinguish or filter workflows triggered by branch deletion versus standard pushes, you can inspect the payload property github.event.deleted, which is a boolean [4][5]. A typical approach to prevent a workflow from running on branch deletion is to use a conditional check: if: ${{!github.event.deleted }} [1] 3. Alternative Events: If you specifically need to respond to the deletion of a branch, the delete event is the dedicated trigger [2][3]. This event provides the name of the deleted ref directly in the event context via github.event.ref [8][9]. 4. Branch Filters: While you can use the branches filter in the push event configuration to restrict when a workflow runs, this filter evaluates against the branch ref being pushed [10]. Because branch deletion triggers a push event context that effectively points to the default branch, branch filtering may not behave as expected for "deleted branch" logic, reinforcing the need to use the github.event.deleted flag or the delete event instead [1].
Citations:
Exclude branch-deletion push events.
When GitHub emits a
pushevent for a deleted branch,github.event.deletedistrueandgithub.event.head_commitisnull. Thebranches: ['**']filter does not exclude this event. With the feature flag enabled, this job can send an email without head commit data.Proposed fix
🤖 Prompt for AI Agents
Source: MCP tools