-
-
Notifications
You must be signed in to change notification settings - Fork 0
chore(ci): repoint push-email-notify to smtp-notify-action #68
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
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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/chapeliser
Length of output: 2409
🌐 Web query:
site:docs.github.com/en/actions push event branch deletion branches filter head_commit null GitHub Actions workflow syntax💡 Result:
When a branch is deleted in a GitHub repository, it generates a push event where the head_commit SHA is null (often represented as a series of zeros, e.g., 0000000000000000000000000000000000000000) [1]. Because this push event technically involves a change to the repository refs, it can trigger workflows configured with the push trigger [1][2]. In this scenario, the head_commit object in the GitHub Actions event context (github.event.head_commit) will be null [1]. If your workflow relies on accessing properties of the head_commit (such as the commit message or author), the workflow may fail unless you include a conditional check to verify the existence of the commit object [3]. You can prevent workflows from running on branch deletions by using a filter or conditional logic within your workflow configuration: 1. Using a conditional step: You can skip specific steps in your job by adding an if conditional that checks if the commit SHA is present: if: ${{ github.event.head_commit!= null }} 2. Using workflow filters: While you cannot directly filter out branch deletions in the push event trigger syntax using standard branches filters, you can structure your workflow to handle the event type appropriately or rely on the fact that GitHub Actions workflows triggered by deletions may behave differently regarding the available refs [1]. For operations specifically related to branch deletions, it is recommended to use the delete event trigger rather than the push event, as the delete event is explicitly designed for this purpose and provides a distinct webhook payload [1]. If you use the delete event, you can configure your workflow to run only when a branch is deleted [1].
Citations:
Exclude branch-deletion pushes.
push.branches: ['**']does not testgithub.event.deleted. A branch deletion can therefore run this job withgithub.event.head_commit == nulland no commit message. Addgithub.event.deleted == falseto the job condition.Suggested change
🧰 Tools
🪛 zizmor (1.29.0)
[warning] 13-16: insufficient job-level concurrency limits (concurrency-limits): workflow is missing concurrency setting
(concurrency-limits)
🤖 Prompt for AI Agents
Source: MCP tools