Skip to content
Discussion options

You must be logged in to vote

First thing I’d do is open the pull request and check exactly which checks are failing. If it’s CI, I’d click into the failed job and read the logs instead of guessing — most of the time it’s something simple like a test failing, a missing env variable, or a lint rule breaking the build.

If GitHub is complaining about merge conflicts, I’d pull the latest main branch into my local branch, fix the conflicts manually in the files, test everything locally, and then commit those fixes. After pushing again, the PR usually updates automatically.

I’d also double-check that the PR branch actually has permission to run workflows, especially since it’s a private repo — sometimes GitHub blocks action…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@dumbozxx
Comment options

Answer selected by dumbozxx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility Making GitHub useable for members of the disability community Issues Repository issues let you track features, problems, and more alongside your code Question Ask and answer questions about GitHub features and usage
2 participants