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
PawelLipski opened this issue
May 5, 2024
· 0 comments
Labels
statusRelates to how status is renderedtraverseRelates to how tree traversal is performedusabilityRelates to user experience, clarity, learning curve, reducing confusion etc.
This is state is already kind-of supported via git machete slide-out --removed-from-remote. In this command, a branch is considered removed from remote when both conditions are true:
git config key branch.BRANCH.merge is set
remote branch pointed by this git config key doesn't exist in refs/remotes.
More precisely, slide-out --removed-from-remote only slides out a removed-from-remote branch when it also doesn't have any downstream branches.
Currently, such branches are just considered untracked.
This new state would need to be handled in:
status
traverse (suggest sliding out, not push)
git{hub,lab} create-{pr,mr} — TBD what to do with such branches.
IntelliJ plugin.
The text was updated successfully, but these errors were encountered:
PawelLipski
added
traverse
Relates to how tree traversal is performed
status
Relates to how status is rendered
usability
Relates to user experience, clarity, learning curve, reducing confusion etc.
labels
May 5, 2024
statusRelates to how status is renderedtraverseRelates to how tree traversal is performedusabilityRelates to user experience, clarity, learning curve, reducing confusion etc.
This is state is already kind-of supported via
git machete slide-out --removed-from-remote
. In this command, a branch is considered removed from remote when both conditions are true:branch.BRANCH.merge
is setrefs/remotes
.More precisely,
slide-out --removed-from-remote
only slides out a removed-from-remote branch when it also doesn't have any downstream branches.Currently, such branches are just considered untracked.
This new state would need to be handled in:
status
traverse
(suggest sliding out, not push)git{hub,lab} create-{pr,mr}
— TBD what to do with such branches.The text was updated successfully, but these errors were encountered: