You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
There are cases where you don't want git trac try doing self.git.fetch('trac', 'develop').
E.g. I need (sage's) #16440 to build docs, while the current 'develop' does not have it merged. Perhaps 'try' should get an option to specify that develop should not be used as the base.
The text was updated successfully, but these errors were encountered:
If you need another fix to build the docs, say, then you can just "git merge docbuild-fix" after "git try ...". There is no need for an alternate UI for that.
well, this would potentially produce differently looking conflicts, as only conflictless merges commute . Logically, one would like to check whether the new ticket conflicts with the existing work branch, not the other way around.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are cases where you don't want git trac try doing self.git.fetch('trac', 'develop').
E.g. I need (sage's) #16440 to build docs, while the current 'develop' does not have it merged. Perhaps 'try' should get an option to specify that develop should not be used as the base.
The text was updated successfully, but these errors were encountered: