ci: trigger workflows on main as well as master (prep for branch rename) - #36
Merged
Merged
Conversation
Prep for the default-branch rename master -> main (required for the sindresorhus/awesome listing). Triggering on both branches keeps CI gapless regardless of when the rename happens; the master entry can be dropped once the rename is complete.
Cafe137
approved these changes
Jul 31, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Preparation for renaming the default branch
master→main(the last prerequisite before submitting awesome-swarm to the official sindresorhus/awesome listing — their checklist requiresmain).What this does
Updates the push triggers in both workflows to fire on both
masterandmain:.github/workflows/awesome-lint.yml.github/workflows/list-health.ymlWhy
The rename is admin-only and happens in repo Settings, which does not edit workflow YAML. If the triggers stayed pinned to
master, the push-to-default CI run would stop firing the moment the branch is renamed. Triggering on both names makes the change order-independent — CI stays green whether this merges before or after the rename, with zero gap.Once the rename is done, a trivial follow-up can drop
masterfrom the list.No behaviour change otherwise;
pull_request,workflow_dispatch, and the weeklyscheduletriggers are untouched.