Attempt fix release preprocessor step #25
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's a permissions issue with the release preprocessing step where it can't commit the changes back to
mainbecause the branch is protected. This PR adds a GitHub bot token and key during checkout to hopefully give it the necessary permissions (I've granted this app access to bypass it in the repo settings).The variables are restricted to an environment which only applies to the main branch in order to avoid them being used to bypass the protections by anyone. That means I also won't be able to test if this works until after I merge this PR, so I will likely need another follow-up PR to fix any bugs.