Add Workflow to Sync With Upstream Rust #15
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.
For #14.
This PR introduces a workflow that automates syncing with the upstream Rust repo.
What this does:
The idea here is that the stable releases are followed.
Stable Rust releases are normally made 6 weeks apart. I didn't think it would be necessary to precisely match this 6-week clockwork, so it checks every week instead.
The latest stable release in the upstream stable branch is branched off master and diverges.
The point of syncing only up to the commit where the stable branched off is to minimize conflicts.