push-protected
push-protected copied to clipboard
CasperWA
GitHub Action to push newly created commit(s) to a protected branch, waiting for status checks to succeed
I've given PAT for the single repo which settings rights. It successfully commits to a protected branch, as expected. However, when I enable enforce commit signing, it fails with "Commits...
I'm using this with commits that have already passed checks, I don't want to wait for any checks to succeed, I only want to immediately push branch A to branch...
The ownership left in `.git` configuration directory after push belongs to `root`: ``` ... total 12 drwxr-xr-x. 2 root root 4096 18 sept. 16:34 . drwxr-xr-x. 3 root root 4096...
RuntimeError: Response did not return the expected status code from request 'https://api.github.com/repos/myorg/myrepo/branches/main'. Status code: 401 (expected: 200). Response: {'message': 'Bad credentials', 'documentation_url': 'https://docs.github.com/rest'}
Several things have happened on the side of GH and their security and permissions handling when interacting with the REST API. Specifically, they have introduced [fine-grained PATs](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#fine-grained-personal-access-tokens). Other fine-grained options...
We are getting this error when trying to push: ``` Waiting for status checks to finish for 'push-action/5028480720/26851-6198-25830' ... ReadTimeout: HTTPSConnectionPool(host='api.github.com', port=443): Read timed out. (read timeout=10) Waiting for status...
thank you for this amazing workflow! it's the best solution i've ever seen. recently GitHub launched a feature that allows specific actors to bypass required pull requests: so i think...
Currently, the action only works for branches protected with checks from GitHub Action workflows. This issue is here to remind that this action should be extended to handle non-GitHub Action...
