Repository navigation
chore(ci): repoint push-email-notify to smtp-notify-action #49
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,46 @@ | ||
| # SPDX-License-Identifier: MPL-2.0 | ||
| # This workflow is managed by gh actions-lock. | ||
| # This workflow is managed by gh actions-lock. | ||
| # Dormant push-email notification. ARMED by setting the repo variable | ||
| # PUSH_EMAIL_ENABLED=true (the single on/off switch). Addresses are pre-filled; | ||
| # sending needs the org SMTP secrets (SMTP_HOST/PORT/USER/PASS). Inherited by | ||
| # new repos from the template; placed on existing repos by the farm sweep. | ||
| # | ||
| # Re-landed after the 2026-07-20 notification-storm freeze (removed in | ||
| # 09f94c5), now on hyperpolymath/smtp-notify-action: Node-free, the SMTP | ||
| # session is Idris2-specified and machine-checked, the binary is Zig-built, | ||
| # byte-reproducible, and SHA-256-pinned inside the action itself. | ||
| name: Push email notification | ||
| on: | ||
| push: {} | ||
| push: | ||
| # Branch pushes only: tag and deletion payloads mislabel Branch:/head_commit. | ||
| branches: ['**'] | ||
| concurrency: | ||
| # Deliberately per-RUN, so no run is ever queued behind another and none is | ||
| # ever cancelled. Do NOT "tidy" this into a shared group such as | ||
| # ${{ github.workflow }}-${{ github.ref }}. GitHub's workflow-syntax docs: | ||
| # "By default, any existing pending job or workflow in the same concurrency | ||
| # group will be canceled and the new queued job or workflow will take its | ||
| # place." That happens regardless of cancel-in-progress, which governs only | ||
| # the RUNNING job. On this workflow it silently loses a notification email, | ||
| # with no error anywhere. Every run here reports a DISTINCT commit, so there | ||
| # is no redundant work for a concurrency limit to remove. | ||
| # The docs also offer `queue: max` (up to 100 pending); not used, because 100 | ||
| # is still a cap whereas a per-run group needs none. | ||
| # Verified with zizmor 1.30.0: deleting this block raises concurrency-limits; | ||
| # this form silences it exactly as a shared group would. | ||
| group: push-email-${{ github.run_id }} | ||
| cancel-in-progress: false | ||
| permissions: | ||
| contents: read | ||
| jobs: | ||
| notify: | ||
| name: Email on push | ||
| if: ${{ vars.PUSH_EMAIL_ENABLED == 'true' }} | ||
| runs-on: ubuntu-latest | ||
| timeout-minutes: 5 | ||
| steps: | ||
| - name: Send push notification email | ||
| uses: dawidd6/action-send-mail@v3.12.0 | ||
| uses: hyperpolymath/smtp-notify-action@v0.2.0 # NOSONAR — pin authority is actions.lock (sha1-ede1191ef6ff3ac02c4f4d9efdf837ee517e11d7) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win 🔎 Supported by static analysis🏁 Script executed: #!/bin/bash
set -eu
printf '%s\n' '--- workflow ---'
cat -n .github/workflows/push-email-notify.yml
printf '%s\n' '--- action pin ---'
rg -n -C 3 'hyperpolymath/smtp-notify-action|smtp-notify-action' .github/workflows/actions.lock .github/workflows . 2>/dev/null | head -120Repository: hyperpolymath/panoply Length of output: 7048 🏁 Script executed: #!/bin/bash
set -eu
for url in \
https://raw.githubusercontent.com/hyperpolymath/smtp-notify-action/v0.2.0/action.yml \
https://raw.githubusercontent.com/hyperpolymath/smtp-notify-action/v0.2.0/README.md
do
printf '\n--- %s ---\n' "$url"
curl -fsSL --max-time 20 "$url" | sed -n '1,220p'
doneRepository: hyperpolymath/panoply Length of output: 5888 Confirm the SMTP transport configuration before merging. If 🤖 Prompt for AI AgentsSource: MCP tools |
||
| with: | ||
| server_address: ${{ secrets.SMTP_HOST }} | ||
| server_port: ${{ secrets.SMTP_PORT }} | ||
|
|
||
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/panoply
Length of output: 6668
🌐 Web query:
GitHub Actions push event branch filters branch deletion github.event.deleted head_commit null💡 Result:
In GitHub Actions, a branch deletion event is surfaced as a push event with a specific payload structure [1][2]. When a branch is deleted, GitHub triggers a push event where the payload includes
deleted: true[1], and thehead_commitobject is typicallynull[1]. Because this is a push event, it can trigger any workflow configured withon: push[3]. If your workflow has branch filters (e.g.,on: push: branches: [...]), the behavior depends on the branch that was deleted. If you need to prevent your workflows from running or failing during branch deletions, you can use a conditional check in your jobs [4][5][6]. Recommended approach: Add a conditionalifstatement to your job to ignore the run when a branch is deleted [4][5][6]: jobs: my_job: if: ${{!github.event.deleted }} runs-on: ubuntu-latest steps: - name: Your step run: echo "Processing..." Key technical details: - Payload: Thepushevent payload containsdeleted: truewhen a branch is deleted [1]. - Head Commit: As noted,github.event.head_commitwill benullin this context [1]. - GITHUB_SHA: When a branch is deleted, the SHA associated with the workflow run often points to the default branch of the repository [7][8]. - Alternative Event: If you specifically want to handle branch deletions, you can use thedeleteevent type instead of (or in addition to)push[7][3][8]. Thedeleteevent payload includes the name of the deleted branch ingithub.event.ref[9]. If you useon: pushand wish to filter by branch, be aware that thepushevent triggered by a deletion may still match your branch filters if the event is technically occurring on a ref that satisfies your criteria [3]. Using the!github.event.deletedguard is the most reliable way to skip these runs [4][5][6].Citations:
Exclude deleted refs before sending mail.
The
pushtrigger also matches branch deletion events. These events setgithub.event.deletedtotrueandgithub.event.head_committonull, so the job can send a notification without commit data. Add!github.event.deletedto the job condition.Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents
Source: MCP tools