jesseduffield.lazygit/pkg/commands
Stefan Haller d890c68cd0 Add ahead/behind information for @{push}
In a triangular workflow the branch that you're pulling from is not the same as
the one that you are pushing to. For example, some people find it useful to set
the upstream branch to origin/master so that pulling effectively rebases onto
master, and set the push.default git config to "current" so that "feature"
pushes to origin/feature.

Another example is a fork-based workflow where "feature" has upstream set to
upstream/main, and the repo has remote.pushDefault set to "origin", so pushing
on "feature" pushes to origin/feature.

This commit adds new fields to models.Branch that store the ahead/behind
information against the push branch; for the "normal" workflow where you pull
and push from/to the upstream branch, AheadForPush/BehindForPush will be the
same as AheadForPull/BehindForPull.
2024-05-19 09:44:38 +02:00
..
git_commands Add ahead/behind information for @{push} 2024-05-19 09:44:38 +02:00
git_config Remove redundant variable dedeclarations 2024-05-19 16:38:21 +10:00
hosting_service Remove redundant variable dedeclarations 2024-05-19 16:38:21 +10:00
models Add ahead/behind information for @{push} 2024-05-19 09:44:38 +02:00
oscommands Remove redundant variable dedeclarations 2024-05-19 16:38:21 +10:00
patch Remove redundant variable dedeclarations 2024-05-19 16:38:21 +10:00
testdata Support opening lazygit in a submodule 2019-05-12 17:59:49 +10:00
types/enums Show mode-specific keybinding suggestions 2024-01-28 08:33:13 +11:00
git.go Add ahead/behind information for @{push} 2024-05-19 09:44:38 +02:00
git_cmd_obj_builder.go Construct arg vector manually rather than parse string 2023-05-23 19:49:19 +10:00
git_cmd_obj_runner.go Retry on index.lock error 2023-07-10 19:13:18 +10:00