Skip to content

Conversation

@andrii0lomakin
Copy link
Collaborator

Motivation:

Currently, Zulip build failure/fix notifications are sent for all branches, which can create noise and reduce the signal value of these notifications. Teams typically only need to be notified about build issues on main protected branches (like develop or main) rather than every feature branch.

This change restricts notifications to only configured main branches, making the notification system more focused and useful.

Changes:

  • Add NOTIFICATION_BRANCHES environment variable at workflow level with a JSON array of branch names that should receive notifications (currently ["develop"])
  • Update notify-failure job condition to check:
    • Event is a push (not PR or merge queue)
    • Branch name is in the NOTIFICATION_BRANCHES list
  • Update notify-fixed job with the same conditions
  • Simplify branch name determination in both jobs by removing merge_group handling (no longer needed since notifications are restricted to push events)
  • Add inline documentation explaining how to add more branches to the notification list

🤖 Generated with Claude Code

Add NOTIFICATION_BRANCHES env variable to configure which branches
receive build failure/fix notifications (currently only 'develop').

- Add conditions to notify-failure and notify-fixed jobs to check
  branch membership and restrict to push events
- Simplify branch name determination by removing merge_group handling
- Make notification branch list easily configurable via JSON array
@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@github-actions
Copy link

github-actions bot commented Feb 2, 2026

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

The env context is not available in job-level if conditions in GitHub
Actions. Switch to vars.MAIN_BRANCHES which is accessible at job level.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@andrii0lomakin andrii0lomakin merged commit daf6adf into develop Feb 2, 2026
70 checks passed
@andrii0lomakin andrii0lomakin deleted the only-main-branches-notifications branch February 2, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants