Automate cargo-generate branch updates
#263
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
This reverts commit a64b82c.
Thanks, Jan! Co-authored-by: Jan Hohenheim <[email protected]>
|
This is what my token looks like: 
Save value as 
|
benfrankel
requested changes
Aug 15, 2024
There was a problem hiding this comment.
The double quotes / curly braces are technically not required here, but it's good form to use them anyways to avoid subtle bugs in situations where they are required, or if assumptions are invalidated in the future.
PR seems reasonable to me otherwise. We can test it out in practice and fix issues if any arise.
janhohenheim
approved these changes
Aug 15, 2024
Co-authored-by: Ben Frankel <[email protected]>
benfrankel
approved these changes
Aug 15, 2024
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.
Closes #129.
This adds
cargo-generate.yaml, a workflow that will automatically merge new changes frommainto thecargo-generatebranch.This will require someone with write access to this repo to create a personal access token with write permissions for "Contents" and "Workflows". I cannot use my own, since I don't have write access. I recommend creating a scoped token that can only write to this specific repository.
This workflow will automatically create an issue on a merge conflict. For an example, see https://github.com/BD103/bevy_quickstart/issues/4.