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
I'd really like to be able to triage local work for not yet being sync'd with upstream or push remotes. I want a subcommand called out-of-sync that will do it for me!
For each local branch, determine whether it is "out of sync":
Get the hash of the local, upstream, and push refs' commits, where applicable, probably using something like git rev-parse.
If there's only a local commit, then
Let all hashes associated with branches determined to be "out of sync" from the previous step be called $branches.
If $branches is empty, exit with a return status of 0.
Otherwise, run the equivalent of git-glimpse select $branches, and exit with a return status of 0.
This seems to overlap slightly with tools like brandon-rhodes/uncommitted, though they focus on crawling filesystems for repositories and indicating that something is out-of-sync. Here, we only focus on a single repository, like all other subcommands.
The text was updated successfully, but these errors were encountered:
I'd really like to be able to triage local work for not yet being sync'd with upstream or push remotes. I want a subcommand called
out-of-sync
that will do it for me!git rev-parse
.$branches
.$branches
is empty, exit with a return status of 0.git-glimpse select $branches
, and exit with a return status of 0.This seems to overlap slightly with tools like
brandon-rhodes/uncommitted
, though they focus on crawling filesystems for repositories and indicating that something is out-of-sync. Here, we only focus on a single repository, like all other subcommands.The text was updated successfully, but these errors were encountered: