git-local-commits

Show commits that haven't been pushed

$ git local-commits

git-local-commits

This command is not a standard Git command but rather a custom script or alias designed to identify and display Git commits present in the local repository but not yet pushed to the remote repository. It typically uses `git log` in conjunction with remote-tracking branches to compare the commit history. The exact implementation depends on the specific script or alias definition. Such scripts can be useful for ensuring that all local changes are backed up and shared with collaborators, preventing data loss or inconsistencies. Using the command regularly allows for maintaining a clean workflow and avoiding unintended divergence from the main development branch. It's crucial to understand how the specific script or alias is configured within your environment to interpret the results correctly, as differing definitions may handle branches or remote names differently.

The command often leverages the capabilities of Git to examine commit ancestry, branch relationships, and remote synchronization status.

Users should verify how the command handles different remote repositories or branches to ensure the output is accurate and aligned with their intended workflow.

This is not a standard Git command; therefore, its behavior may vary greatly depending on its specific implementation (script or alias). Ensure you understand the underlying logic of your `git-local-commits` definition. It might not handle all edge cases, like multiple remote repositories or complex branching strategies, correctly. The command name `git-local-commits` is also only a common convention and may not apply to any given setup.

A simple bash function defining a `git-local-commits` functionality might look like this:

`git-local-commits() { git log --branches --not --remotes; }`

This simplistic version lists commits on local branches but not on any remote. More sophisticated scripts can target a specific remote and branch.

Another common implementation involves comparing the local branch with its upstream remote branch.
For Example:
`git log origin/main..HEAD`

The `git-local-commits` command is usually configured as a Git alias or a standalone executable script within the user's `$PATH`. To create a git alias use
`git config --global alias.local-commits '!git log --branches --not --remotes'`

git log(1), git remote(1), git branch(1), git fetch(1), git push(1)