Record the changes in the working copy, creating a patch
pijul record [-h | --help] [-V | --version] [--repository <repository>] [--branch <branch>] [(-A | --author) <author>] [(-m | --message) <message>] [--depends-on <depends-on>…] [-a | --all] [prefix]…
Record is the only command for creating patches in Pijul.
This command compares the pristine with the working copy, creates a patch, applies it to the pristine, and synchronises file moves.
By default, the comparison happens between the whole pristine and the
whole working copy. It can also be restricted to a list of paths,
If this is the first command to be run after installing Pijul for the first time, a file named ~/.pijulconfig/config.toml will be created, and your author name will be saved there.
When using Pijul, it is highly recommended to sign your patches. Record automatically does this after keys have been setup.
pijul record -a -m "My first patch" -A "me <email@example.com>" src
Print a help message and exit.
Print the version of Pijul and exit.
Don't run this command in the current directory, run it in <repository> instead.
Compare branch <branch>, instead of the current branch, with the working copy.
Set the patch's author. By default, the first patch you create on any repository after installing Pijul saves your author name in "~/.pijulconfig/config.toml".
Add a message to this patch, summarising your changes.
Add a list of dependencies to this patch. Dependencies are normally inferred by Pijul, but some semantic dependencies cannot be inferred. Use this command to add them.
Don't select patches to push interactively, push all patches instead.
Restrict the comparison to a list of paths instead of comparing the whole repository.