Record the changes in the working copy, creating a patch

Record the changes in the working copy, creating a change.

```cmd
pijul record [-h | --help] [-V | --version] [--repository <repository>] [--branch <branch>] [(-A | --author) <author>] [(-m | --message) <message>] [--depends-on <depends-on>…] [-a | --all] [prefix]…

```
cmd pijul record [-h | --help] [-V | --version] [-S] [--stdin] [--tag] [-a | --all]
[--amend <amend>] [(--author) <author>] [--channel <channel>]
[(-m | --message) <message>] [--repository <repository>]
[--timestamp <timestamp>][prefix]…

Record is the only command for creating patches in Pijul.

Record is the only command for creating changes in Pijul.

This command compares the pristine with the working copy, creates a
patch, applies it to the pristine, and synchronises file moves.

This command compares the pristine with the working copy, creates a change,
applies it to the pristine, and synchronizes file moves.

A patch is then saved to .pijul/patches (from the root of the
repository), and can later be exchanged with
[push](./reference/push.html) and [pull](./reference/pull.html).

A change is then saved to .pijul/changes (from the root of the repository),
and can later be exchanged with [push](./push.md) and [pull](./pull.md).

By default, the comparison happens between the whole pristine and the
whole working copy. It can also be restricted to a list of paths,

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.

See [Getting started](../getting_started.md) part of the documentation on how to
set up author for pijul record.

patches. Record automatically does this after [keys have been
setup](./signing_patches.html).

changes. Record automatically does this after [keys have been
setup](../signing_changes.html).
## Using `$EDITOR` to edit the change

## Interative use

If running in default mode (without `-a` or `--all` flag) pijul will start the
default editor (based on `$EDITOR` environment variable) to edit the change
properties. You can modify:
  - change message,
  - timestamp,
  - authors,
  - dependencies,
  - and changes to record.

When `pijul record` is invoked interactively, the user will be asked a
series of questions with the prompt `[ynkad]`. The possible answers are:
* `y`: include the change in the patch.
* `n`: don't include the change in the patch.
* `k`: undo the previous answer and go back to the previous change.
* `a`: include all the following changes in the patch.
* `d`: do not include any of the following changes in the patch.

Changes are numbered, but You do not have to fix numbering after deleting those
parts You do not want to record.

## Examples

## Example

pijul record -a -m "My first patch" -A "me <me@example.com>" src

pijul record -a -m "My first change" --author "me <me@example.com>" src

- --amend \<amend\>

  Append the new recording to the change identified by \<amend\>.

- --branch \<branch\>

- --channel \<channel\>

  Compare branch \<branch\>, instead of the current branch, with the

  Compare channel \<channel\>, instead of the current channel, with the

- -A, --author

- --author

  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".

  Set the change's author.

- -m, --message

- --timestamp

  Add a message to this patch, summarising your changes.

  Use \<timestamp\> for the change instead of current time.

- --depends-on \<depends-on\>

- -m, --message

  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.

  Add a message to this change, summarizing your changes.

  Don't select patches to push interactively, push all patches
  instead.

  Don't select changes to push interactively, push all changes instead.