digidem / mapeo-core-next

The upcoming version of Mapeo Core
MIT License
7 stars 1 forks source link

Fix doc auto-commit error when releasing #707

Open EvanHahn opened 2 weeks ago

EvanHahn commented 2 weeks ago

I just tried to do a release and got the following error:

[main 0b21c4a] docs: update API docs
 Author: EvanHahn <EvanHahn@users.noreply.github.com>
 21 files changed, 260 insertions(+), 121 deletions(-)
INPUT_TAGGING_MESSAGE: 
No tagging message supplied. No tag will be added.
INPUT_PUSH_OPTIONS: 
remote: error: GH006: Protected branch update failed for refs/heads/main.        
remote: error: Changes must be made through a pull request.        
To https://github.com/digidem/mapeo-core-next
 ! [remote rejected] main -> main (protected branch hook declined)
error: failed to push some refs to 'https://github.com/digidem/mapeo-core-next'
Error: Invalid status code: 1
    at ChildProcess.<anonymous> (/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v5/index.js:17:19)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  code: 1
}
Error: Invalid status code: 1
    at ChildProcess.<anonymous> (/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v5/index.js:17:19)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)

(See the full logs.)

It seems that we can't auto-commit to main here because the branch is protected. We should fix this. (Not sure how right now; just filing the issue.)