Push rejected due to branch protection rule

[JohnWhitmire]

Discussion Type

Product Feedback

Discussion Content

Hello, everyone.
I have met some errors during merge data.
How can I fix it.
remote: error: GH014: Push rejected due to branch protection rule
remote:
remote: - Required status checks are failing.
remote: ————————————————————————————————————————————————
remote: The following checks didn’t pass:
remote: - build-and-test
remote: - lint
remote:
remote: Please ensure all required checks pass before pushing to the protected branch.
remote:
remote: Learn more about branch protection rules:
remote: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/about-protected-branches
Please someone help me.

[PRIYAtechky]

The error means your branch is protected, and GitHub won’t allow merging until all required checks pass.

To fix it:

1. Run the failing checks locally (build-and-test, lint) and resolve any errors.
2. Commit and push the fixes so the checks pass in CI.
3. Once all checks are green, you’ll be able to merge.

If you don’t control branch protection, you may need to ask a repository admin to adjust the rules.

🔗 Branch protection rules docs

[mecodeatlas]

Thanks for posting in the GitHub Community, @PierreAndre8099!

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the Repositories category. I've gone ahead and moved it for you. Good luck!

[Kusk24]

You’re pushing to a protected branch and the required checks (build-and-test, lint) aren’t green. GitHub blocks the push (GH014) until those pass.

Fix steps

1. Run locally: make the CI pass locally (e.g., npm test / pytest / go test and your linter).
2. Use a PR: push to a feature branch and open a pull request so checks run on the PR.
3. Match check names: ensure your workflow job names match the rule (or update the rule to the current job names). Stale/renamed checks won’t satisfy protection.
4. Re-run checks / update branch: re-run from the Checks tab and bring your branch up to date (rebase/merge) if required.
5. If you’re an admin: temporarily relax the rule or use admin override (org policy permitting).

Previous cases (similar):

1. Checks renamed → rule still expects old names; fix by aligning job names or rule. #26668
2. Direct pushes blocked even for allowed actors when required checks are enabled—use PR/CI, or admin bypass. #23273

[nitinscodehub]

1️⃣ Check aur fix errors locally

Terminal me repo root pe ja:

cd /path/to/your/repo

Required checks run kar:

Node.js project example

npm install # dependencies install
npm test # build-and-test check
npm run lint # lint check

Jo bhi errors aaye, unko fix kar aur save kar.

2️⃣ Commit changes
git add .
git commit -m "Fix build-and-test and lint errors"

3️⃣ Push to a feature branch, not directly protected branch
git checkout -b my-feature-branch
git push origin my-feature-branch

4️⃣ Open a Pull Request (PR)

GitHub pe jaake PR create kar from my-feature-branch → protected-branch.

CI automatically checks run karega.

Jab build-and-test + lint green ho jaye → merge kar de.

💡 Important points:

Protected branch me direct push nahi hota jab required checks fail ho.

Always fix errors locally → push feature branch → open PR.

Agar check names changed hai, workflow ya branch protection rules update karna pad sakta hai.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬