This repository was archived by the owner on Oct 25, 2024. It is now read-only.
Closed
Conversation
Contributor
Author
|
Note that exposing |
In response to the discussion in #197. Allows app code to mutate the history safely despite the raciness of asynchronous transitions.
Contributor
|
I like this alot. |
Contributor
Author
|
Offline discussion w/@loganj, we're reluctant to open this up hook without thinking about it a bit more. Is the queue really something we should be exposing even more like this, or would that get in the way of a longer term vision that eliminates the need for it? |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
In response to the discussion in #197. Allows app code to mutate the history
safely despite the raciness of asynchronous transitions.