How do I disable the push command for only some repositories?

[jamesharris-garmin]

I am a gerrit user/administrator and directly pushing to the branch I am working on is a bad idea, but I some times need to be able to do this so I can push history when mirroring repositories.

Is there a way to write a custom command that changes its behavior depending on the current state of the repository.

I would like a command that does the following:

if there is a remote named gerrit in the repository, push to the gerrit review as described in the custom commands section. Otherwise push directly.

I assume this is possible with go templating but if someone has an example that would be fantastic.

One other use case for conditional language in custom command templates is this:

Say I use the tool git-review to publish a commit to gerrit. This tool automatically rebases your patches before pushing to gerrit. The automatic rebase behavior breaks if you are trying to push a merge commit (rebasing a merge makes no sense). So in those cases I have to pass the -R flag to push without a rebase.

So I only want to push -R if I am not in a rebase.

Part of this is I suck at ergonomic keyboard design in TUI or I would bind everything to a separate function or menu.

[stefanhaller]

Are you adding/deleting the gerrit remote dynamically, or is it just that some of your repos have one and others don't? If it's the latter, you can define a custom command specific to a given repo by putting it into a .git/lazygit.yml file in that repo (same for all other lazygit configs, of course).

[jamesharris-garmin]

so I work on some android open source project trees which have over a thousand repositories in them. so it would be much more convenient to have a global way to construct it that could autodetect the solution.

Ideally I would re-configure it when my remotes pointed at one of my companies gerrit servers.

[jamesharris-garmin]

I don't know if lazygit's go templating system is powerful enough to handle conditional statements. (I have used chezmoi and that tool uses some extensions to provide powerful conditional support.

[stefanhaller]

If it applies to all repos in the tree, you can also put the lazygit.yml file in their parent folder.

The problem with defining the command in a dynamic way is that it's not possible to say "use lazygit's default push command"; we'd need #4753 for that. The best you could do is call git push, but that's not the same, as it doesn't do lazygit's force-push detection.

[jamesharris-garmin]

I feel like the simpler approach here would be to provide template functions that let you call back into default APIs.

The parent folder thing might be incredibly useful here.

Another thing I would have liked would be to configure my command to only add an argument if there is an un-published merge commit in the history.

I'll add that to the description to see what we think of that because that would be saner.