Batched push #71
Merged
Batched push #71
Conversation
This file contains hidden or 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
Merged
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.
Continues #53, extending
Repo.Push()to accept varargs[]updater.Updater.This allows batched updates to include details about every update, replacing the generic "multiple updates" placeholders and finishing a
TODO.In
GitHubRepo.Push(), the{major:, minor:, patch:}visible blob in PRs is replaced with an invisible HMAC-ed blob that encodes the full update details.This will eventually be parsed, bringing back the ability to skip updates that have closed PRs. Previously that relied on parsing the target update from branch names, but that branch naming became optional with batched updates.