NAME

repomatic git-commit-push - Commit files and push, rebasing on rejection

SYNOPSIS

repomatic git-commit-push [OPTIONS] [PATHS]...

DESCRIPTION

Commit the given files and push them to a remote branch.

Idempotent: exits successfully without creating a commit when the files are unchanged. A rejected push (something else pushed meanwhile) is retried after rebasing onto the fresh remote tip, so release jobs can publish generated files to the default branch without racing other pushes. Works from a detached HEAD.

With --all-changes, everything the working tree carries is staged rather than a named list. Reserved for a job whose writers are the steps right before it and whose output paths only its configuration knows.

[PATHS]...

OPTIONS

--message TEXT

Commit message.
[required]

--remote TEXT

Remote to push to.

--branch TEXT

Remote branch to push to.

--all-changes / --no-all-changes

Stage every change in the working tree instead of named files, for a job whose output paths come from configuration.

--help / -h

Show this message and exit.

ENVIRONMENT

GIT_COMMIT_PUSH_MESSAGE

Commit message.

GIT_COMMIT_PUSH_REMOTE

Remote to push to.

GIT_COMMIT_PUSH_BRANCH

Remote branch to push to.

GIT_COMMIT_PUSH_ALL_CHANGES

Stage every change in the working tree instead of named files, for a job whose output paths come from configuration.

GIT_COMMIT_PUSH__CLICK_DEFAULT_HELP

Show this message and exit.

EXIT STATUS

0

Success.

1

A runtime error, or an aborted prompt (Ctrl-C, a declined confirmation).

2

A usage error: unknown option, invalid value, missing operand, or an unparsable configuration file.

EXAMPLES

Commit two files and push

repomatic git\-commit\-push \-\-message "Record v1.2.3 binaries" docs/binaries.md docs/assets/virustotal\-scans.csv

Commit every change in the tree

repomatic git\-commit\-push \-\-message "Sample star counts" \-\-all\-changes

AUTHORS

Kevin Deldycke