-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ghstack should submit the current rev and lower in the stack and not the entire stack. #283
Comments
(on a new stack created just like before)
|
Seems like this has been brought up on ghstack already: ezyang/ghstack#101 |
Looks like HEAD in ghstacks is a bit different than what i literally translates to when doing branless/trunk development. Here is a log of The interesting line is
https://github.com/facebook/sapling/blob/main/eden/scm/ghstack/sapling_shell.py#L67-L74 I think this is not the correct translation for HEAD in call cases and HEAD in this case should actually mean "current commit" (i.e Thoughts? |
My workflow for
sl
(from years ofhg
inside FB) is to.sl split
to split those out into logical testable/reviewable stages.So usually I am never just submitting one giant stack, but iterating on a current stack. I usually will submit one PR/Diff at a time and then work on fixing the next one and submit it.
Running
sl ghstack submit
however just took everything in my stack and made a PR for each one. This is not ideal as usually at the top of my stack i have a "scratch" commit of random stuff that needs to be split or cleaned up before submitting.I think
sl ghstack submit
should either take a rev as an option or use the current rev in the stack I am in and submit all the revs below it and none of the ones on top.You can see that a PR was created for WIP which is wrong and will almost (in my workflow) never be used. Right now i need to close that WIP PR as it will never ever be reviewable. (also showing the world the mess that is my head and development processes).
Looking through the options of hgstack this doesn't seem to be an option either.
The text was updated successfully, but these errors were encountered: