Closed benlubas closed 10 months ago
This seems correct? I don't know much about the gh pipeline but it makes sense that panvimdoc would add a commit to main to update vimdoc after any merge into main
currently it's running in the PRs and adding to them. The vimdoc changes then get merged with the rest of the PR. And then it tries to run in main, and fails b/c it doesn't have permission I think b/c it's a protected branch.
Ahh gotcha, that makes sense. In theory then we should be able to move the doc generation up the pipeline before it's merged onto main (I assume this is what you are looking into). Alternatively, I imagine there is a way to allow a bot to have direct write access to a protected branch in github
move the doc generation up the pipeline
It's already running in PRs, you can see it committed to the PR that I added it in
seems like we need to tell it not to do that.. will look at it