All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
9.0.0 - 2022-03-11
- [BREAKING] The action will now fail when the
git commit
command fails. (#370) - [BREAKING] The action won't try deleting and re-creting tags when it fails to push them, it's now up to you to set the proper arguments (see the
tag_push
input). (#367)
tag_push
input: you can now set the arguments of thegit push --tags
command.tag_pushed
output: whether the action pushed tags.
8.0.2 - 2022-02-07
- The
commit
input is now properly listed in the README. (#360)
8.0.1 - 2022-01-23
- Fixed a bug that prevented the
--allow-empty
flag from being used for thecommit
input. (#352) - Fixed README and CHANGELOG docs for the
pull
input, that were still showing the option to useNO-PULL
to prevent pulling (while now it's the default behavior). (#354) - Added a paragraph to the FAQs section of the README, that explains how to work with PRs in v8. (#351)
8.0.0 - 2022-01-20
- [BREAKING] The action will now work with whatever ref has been checked out, without pulling or switching branches by default. You can still pull using the
pull
input and create a new branch with the newly-addednew_branch
input. For more info, check commit6fdb34e
.
- [BREAKING] The
signoff
input has been removed, usecommit
instead. (#331) - [BREAKING] The
pull_strategy
input has been removed, usepull
instead. - [BREAKING] The
branch
andbranch_mode
inputs have been removed, check commit6fdb34e
for more info. - [BREAKING] The
pull
input doesn't supportNO-PULL
anymore: if you don't want the action to pull, simply remove the input, as it's the default behavior now.
- Added the
commit
input, that allows you to change the arguments for thegit commit
command. (#331) - Added the
new_branch
input. (6fdb34e
) - Added the
commit_long_sha
output. (#349)
7.5.0 - 2021-12-03
- Support remote branch creation: use the
branch_mode
input to make the action create a new branch when there's no branch with the given name on the remote (#329)
7.4.0 - 2021-09-30
- Added
pull
input: you can use it to change the arguments of thegit pull
command (#294)
- Deprecated
pull_strategy
: usepull
instead (#294)
7.3.0 - 2021-09-06
- Added custom committer support via the
committer_name
andcommitter_email
inputs (#264) - Added
commit_sha
output (#275) - Added
pathspec_error_handling
input (#280)
7.2.1 - 2021-05-11
- Fixed an issue with missing outputs (#189)
7.2.0 - 2021-04-22
default_author
: this input allows you to control how the action fills missing author name or email (issue #167)github_token
input introduced to get token to use in API calls
- Git args are now parsed with
string-argv
, the format has to comply with what the package can parse (issue #179)
7.1.2 - 2021-04-16
- Git args parsing now correctly handles quotes, that can be used for multi-word arguments (issue #166)
7.1.1 - 2021-04-04
- Git args parsing has been improved, and now handles spaces correctly (issue #154)
7.1.0 - 2021-03-03
pull_strategy
: you can use 'NO-PULL' to prevent the action from pulling from the remote at all.
7.0.0 - 2021-01-16
- [BREAKING] The token input has been removed: author info will be filled using the GitHub Actor, instead of fetching info from the GitHub API.
The commits will be authored using the GitHub no-reply email associated with the account: [email protected] - [BREAKING] Because of the change above, the author will now be the user that triggered the action run, and not the author of the last commit: while the two are often the same person, there are instances where they might differ (e.g. when a workflow run is triggered manually).
6.2.0 - 2020-12-23
push
input: allow for customgit push
arguments to be used, more info in the README. (issue #100)
6.1.0 - 2020-12-22
token
input: you can now use this instead of setting theGITHUB_TOKEN
env variable, which has been deprecated. This input is optional, its default value is the defaultsecrets.GITHUB_TOKEN
. You only need to use this if you want the action to run with a PAT. (issue #110)
GITHUB_TOKEN
: the use of this env variable is now deprecated in favor of thetoken
input, you'll start receiving warnings if you keep using it. (issue #110)
6.0.0 - 2020-12-22
- (BREAKING?) Multiple git commands: support JSON/YAML arrays for the
add
andremove
parameters (you still need pass a string as input, but that can be parsed to an array by the action). Using them will run multiple commands in succession. I don't think this will be really breaking anything, but I've used a major version change just to be sure. There's more info about this stuff on the README. (issue #95)
5.3.0 - 2020-12-12
- Outputs: the action now has 3 outputs (
committed
,pushed
, andtagged
) that will be set to eithertrue
orfalse
to tell you what the action has done. The outputs are also shown in the action logs.
5.2.0 - 2020-11-11
- New
push
option: this lets you tell the action whether to push commit and tags to the repo. The default value istrue
, so that the default behavior is not changed. (issue #86)
5.1.2 - 2020-11-10
- Fixed an issue with the build (issue #88)
5.1.1 - 2020-11-07
- Fixed typo in parameter name:
pull_strategy
was written aspull_stategy
(PR #83)
5.1.0 - 2020-10-07
- The default commit message now displays the name of the workflow too (issue #64)
5.0.0 - 2020-09-27
- [BREAKING] Action parameters: multiple action parameters have been changed, refer to the docs for better info
- The code is now entirely in TypeScript (PR #57)
- Improved input checks
- Logs are now displayed on Windows too
- Remove unnecessary steps
- Remove unused dependencies
4.4.0 - 2020-07-31
- Pull requests: the action can now work in runs triggered by pull request events (issue #48)
4.3.0 - 2020-07-29
signoff
parameter: lets you use the--signoff
argument for thegit commit
command (PR #46)
4.2.1 - 2020-07-10
- OS-support: the action now properly works on Windows instances (issue #33)
4.2.0 - 2020-05-17
- Tagging: you can now create and update lightweight tags (PR #30)
4.1.0 - 2020-05-01
ref
parameter: lets you choose the branch to run the action on, the default is the one that triggered the workflow (issue #29)
4.0.3 - 2020-05-01
- Logs:
git diff
won't display logs anymore, to avoid buffer problems (issue #27) - Logs: additional info will be logged along with the command outputs
- Logs: added groups to improve readability
4.0.2 - 2020-04-19
- Error handling: failures are now easier to read (issue #25)
4.0.1 - 2020-03-20
- Scheduled events: the action can be used in action runs triggered by a scheduled events
- Warnings: there won't be warnings when both
author_name
andauthor_email
are set
4.0.0 - 2020-03-03
- [BREAKING]
path
parameter: see 'Changed' section for more info - [BREAKING]
pattern
parameter: see 'Changed' section for more info
- The action now uses
git add
andgit rm
commands, you can choose their arguemnts directly by using theadd
andremove
parameters - [BREAKING] Error handling: the action won't stop if one of your git commands fails (e.g. if one of your pathspecs doesn't match any file)
3.1.0 - 2020-02-21
remove
parameter: lets you delete files directly from the action
3.0.0 - 2020-01-24
- The action can now run in multiple subsequent jobs in the same workflow
- [BREAKING]
actions/checkout@v1
support is being dropped in favor ofactions/checkout@v2
2.3.2 - 2019-12-29
cwd
parameter: lets you set the Current Working Directory
2.3.1 - 2019-12-20
- Short tags: from now on, there will be short major tags available (
v2
,v3
, ...)
2.3.0 - 2019-12-14
- TypeScript rewrite: the action will run faster because, unlike with Docker, no build process is needed
- OS support: the action can now run in non-Linux environments too
2.2.0 - 2019-12-14
- The action can automatically fetch the commit author to use
- You can manually provide the author using the
author_name
andauthor_email
parameters
2.1.1 - 2019-12-07
- The action can now be used multiple times in the same workflow
2.1.0 - 2019-09-19
force
parameter: uses--force
when runninggit add
2.0.0 - 2019-09-18
- [BREAKING] The action now uses a
find
command
1.0.0 - 2019-09-17
First release