8000 Introduce a new state of branch in `status`/`traverse`: removed from remote · Issue #1242 · VirtusLab/git-machete · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Open
PawelLipski opened this issue May 5, 2024 · 0 comments
Open

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

PawelLipski opened this issue May 5, 2024 · 0 comments
Assignees
@PawelLipski
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
PawelLipski commented May 5, 2024 •
edited
Loading

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 in every context other than slide-out --removed-from-remote.

This new state would need to be handled in:

  • status
  • traverse (suggest sliding out, not pushing; also, don't suggest creating a PR/MR)
  • 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
@PawelLipski PawelLipski added this to the v3.33.0 milestone Jan 14, 2025
@PawelLipski PawelLipski self-assigned this Jan 14, 2025
@PawelLipski PawelLipski linked a pull request Jan 21, 2025 that will close this issue
Tidy up naming in SyncToParentStatus #1390
Merged
@PawelLipski PawelLipski removed this from the v3.33.0 milestone Jan 21, 2025
@PawelLipski PawelLipski removed a link to a pull request Jan 21, 2025
Tidy up naming in SyncToParentStatus #1390
Merged
@PawelLipski PawelLipski mentioned this issue May 13, 2025
Merged
3 tasks
Sign up for free to j 4C94 oin this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PawelLipski PawelLipski

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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PawelLipski
0