Repository navigation
ci: run Checks against master, the branch this repo actually uses - #6
Merged
Merged
Conversation
The Checks workflow fires on development and main, but this repo's default branch is master — main is still the "Initial commit" it was created with and has never taken a change. So every pull request targeting master merges without a single check having run: #4 (development -> master) and the open Dependabot bun group bump #5 both show "no checks reported". Point both triggers at master instead of main. development keeps its trigger, so the feature-branch flow is unchanged; what this adds is coverage on the branch the app is actually released from. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
salmanfarisvp
approved these changes
Sep 25, 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
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.
Problem
.github/workflows/checks.ymltriggers ondevelopmentandmain, but this repo's default branch ismaster.mainis still theInitial commitit was created with (2026-09-17) and has never received a change, whilemastercarries the real history and is whatdevelopmentmerges into.The result is that nothing targeting
masteris ever checked:development→master) merged with no checks.no checks reported on the 'dependabot/bun/bun-cd9fe85f9a' branch— so there is no signal to review it on.gh run list --workflow checks.ymlconfirms it: every run is either apushtodevelopmentor apull_requestintodevelopment. Not one run hasmasteras its base.Fix
Point both the
pushandpull_requesttriggers atmasterinstead ofmain.developmentkeeps its trigger, so the feature-branch flow is unchanged — this only adds coverage on the branch the app is released from.daylight-app is the only Edge App with this mismatch; every sibling repo's
checks.ymlalready lists its own default branch.🤖 Generated with Claude Code