v4.2.1

This release makes the action work also on Windows instances.
Ref: #33

v4.2.0

This release adds tagging: you can now create and update lightweight tags within the action. Check out the "tagging" section of the readme for more info!
Ref #30

v4.1.0

This release adds the ref option, that allows you to tell the action which branch it should use. If none is entered, it will default to the one that triggered the workflow (which is stored by GitHub in the GITHUB_REF env variable).
Please note that you only need to write the branch name, not the whole refs/heads/... string.
Ref issue: #29

v4.0.3

This release improves logs:

• git diff will now stop emitting logs, so that everything is easier to read and won't cause buffer problems (ref issue #27).
• Everything that is supposed to be logged will be: previous versions logged only command outputs and not echo lines. You will now find additional info in the logs.
• To allow you to focus on the most relevant stuff, I grouped everything that only needs to exist to debug the action in a foldable group called "Internal logs".

v4.0.2

This release fixes the error handling, so that action failures are easier to read. Ref: #25

v4.0.1

This release allows the action to also work when using a scheduled event as workflow trigger (fixes #22).
It also prevents the action from logging warnings when both author_name and author_email are set.

v4.0.0

The version gets rid of find commands and path/pattern options: now the action uses git add and git rm commands, and you can directly choose the arguments with the add/remove options.
This version also changes the error handling: if one of the git commands fails the action will not stop. That means that if your git add pathspec doesn't match any file the action can still run the git rm command and vice versa.

v3.1.0

This release add the remove parameter, which allows you to delete files directly from the action.

v3.0.0

This release allows the action to run in multiple jobs, by pulling before creating the new commit.
Please keep in mind that this will work only if the jobs are fired subsequently, it won't work if they are run at the same time: in that case, only the first commit will get pushed, while the other will get rejected by the remote.
To run jobs one after the other you can use the needs parameter: link

Important: this will only work if you're using actions/checkout@v2, using other major versions may not work.

v2.3.2

This release adds the option to change the working directory with the cwd input parameter. This can be useful if you need to commit to a repository that has not been checked out in the GITHUB_WORKSPACE.