Skip to content
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

Introduce a new state of branch in status/traverse: removed from remote #1242

Open
PawelLipski opened this issue May 5, 2024 · 0 comments
Open
Labels
status Relates to how status is rendered traverse Relates to how tree traversal is performed usability Relates to user experience, clarity, learning curve, reducing confusion etc.

Comments

@PawelLipski
Copy link
Collaborator

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:

  1. git config key branch.BRANCH.merge is set
  2. 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.
@PawelLipski 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status Relates to how status is rendered traverse Relates to how tree traversal is performed usability Relates to user experience, clarity, learning curve, reducing confusion etc.
Projects
None yet
Development

No branches or pull requests

1 participant