|
STG-GOTO(1) StGit Manual STG-GOTO(1)
stg-goto - Go to patch by pushing or popping as necessary
stg goto [OPTIONS] <patch>
Go to patch by pushing or popping as necessary
-k, --keep Keep the local changes -m, --merged Check for patches merged upstream --committer-date-is-author-date Instead of using the current time as the committer date, use the author date of the commit as the committer date. --conflicts[=<policy>] Either "allow" or "disallow" pushing a patch with conflicts. Using --conflicts=allow (or just --conflicts) allows pushing a patch that may result in unresolved merge conflicts. The patch will be pushed and files with conflicts will be left with conflict markers to be resolved manually; or the operation undone with stg undo --hard. This is the default behavior and also corresponds to the "stgit.push.allow-conflicts" variable being set to "true". Using --conflicts=disallow disallows pushing any patch that would result in merge conflicts. The operation will stop on the last patch that can be pushed without conflicts. This behavior can be configured by setting "stgit.push.allow-conflicts" to "false".
Part of the StGit suite - see stg(1)
This page is part of the stgit (Stacked Git) project.
Information about the project can be found at
⟨http://www.procode.org/stgit/⟩. If you have a bug report for
this manual page, see ⟨http://www.procode.org/stgit/⟩. This page
was obtained from the project's upstream Git repository
⟨https://github.com/stacked-git/stgit.git⟩ on 2024-06-14. (At
that time, the date of the most recent commit that was found in
the repository was 2024-05-22.) If you discover any rendering
problems in this HTML version of the page, or you believe there
is a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
[email protected]
StGit 2.4.7 06/14/2024 STG-GOTO(1)
Pages that refer to this page: stg(1)