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
Basically, the logic should be that if there was a remote tracking ref that matches the name of a local branch and that gets pruned during a pull, the local branch should be removed if there are no divergent commits.
The text was updated successfully, but these errors were encountered:
Does this happen for any remote or just origin? If the latter, why? Perhaps this should check whether the branch is present in other remotes before pruning?
When pruning, rather than wholly removing, perhaps we just move the branch to a refs/gg-old/BRANCH namespace. The user can periodically clean these out when they want to, but at least there's separation.
Version 1.2 includes features to handle repositories with lots of branches.
### Added
- gg can now be installed via [Nix](https://nixos.org/)!
See https://gg-scm.io/install for instructions.
- `push` and `commit` have a new `-hooks=0` flag.
([#153](#153))
- `pull` has a new `--force-tags` flag.
([#155](#155))
- `branch` has a new `--pattern` flag to filter listed branches.
([#156](#156))
### Changed
- Local branches are moved under `refs/gg-old/` during `pull`
when they are deleted from a remote.
([#118](#118))
### Fixed
- `GIT_EDITOR` is now always invoked from the root of the working copy
to match with the behavior of Git.
([#152](#152))
- `revert` now prints an error message
if used on a nonexistent file in a new repository.
Basically, the logic should be that if there was a remote tracking ref that matches the name of a local branch and that gets pruned during a pull, the local branch should be removed if there are no divergent commits.
The text was updated successfully, but these errors were encountered: