8000 `github_action[bot]` unable to push to main branch · Issue #23 · biomejs/pre-commit · GitHub
[go: up one dir, main page]

Skip to content

github_action[bot] unable to push to main branch #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
yxtay opened this issue Feb 6, 2025 · 0 comments · Fixed by #24
Closed

github_action[bot] unable to push to main branch #23

yxtay opened this issue Feb 6, 2025 · 0 comments · Fixed by #24

Comments

@yxtay
Copy link
Contributor
yxtay commented Feb 6, 2025

https://github.com/biomejs/pre-commit/actions/runs/13170705879/job/36760419046

Error: Command failed: git -C /home/runner/work/pre-commit/pre-commit push origin HEAD:refs/heads/main
remote: error: GH006: Protected branch update failed for refs/heads/main.        
remote: 
remote: - Changes must be made through a pull request.        
To https://github.com/biomejs/pre-commit
 ! [remote rejected] HEAD -> main (protected branch hook declined)
error: failed to push some refs to 'https://github.com/biomejs/pre-commit'

This is regarding #19

It looks like main branch is protected, which is good practice. However, as a result, the scheduled workflow is unable to push the commits. Able to add github_action[bot] and dependabot to the bypass list to allow it to work? I'm not sure what other options are available.

When I tested the workflow, I did not have any branch protection rules on my fork.

Without the tags on the main branch, pre-commit autoupdate will not use the right tags.

> pre-commit autoupdate
[https://github.com/biomejs/pre-commit] updating v1.9.4 -> v0.6.1
@yxtay yxtay changed the title GitHub Action[Bot] unable to push to main branch github_action[bot] unable to push to main branch Feb 6, 2025
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 a pull request may close this issue.

1 participant
0