Alex
Alex
I didn't. BTW, I just removed projects: write permission because it is not need. I missed that you use a separate token.
Just for the reference these are the current permissions one of the workflows runs with: 
> Oh that's interesting @sashashura , thanks! Sure, sounds like a sensible change, let's give it a try 💪 > > Wouldn't our `add-to-project` action need write access to issues,...
Please let me know if you have any questions.
Tried to rename the branch, but it closes the pr. Let me know if that is mandatory.
They are triggered on `pull_request` which already has limited permissions, but you want for consistency I can add!
Just for the reference these are permissions golangci-lint runs with on push: 
Please let me know if you have any questions.
Permissions are not as granular as they could be. `contents: write` covers all the cases you mentioned.
But currently I set contents to read. Do I understand correctly that ``` env: prebuild_upload: ${{ secrets.GITHUB_TOKEN }} run: npx prebuild --runtime napi --target 7 ``` creates GitHub release and...