token input: you can now use this instead of setting the GITHUB_TOKEN env variable, which has been deprecated. This input is optional, its default value is the default secrets.GITHUB_TOKEN. You only need to use this if you want the action to run with a PAT. (issue #110)
Deprecated:
GITHUB_TOKEN: the use of this env variable is now deprecated in favor of the token input, you'll start receiving warnings if you keep using it. (issue #110)
(BREAKING?) Multiple git commands: support JSON/YAML arrays for the add and remove 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)
Outputs: the action now has 3 outputs (committed, pushed, and tagged) that will be set to either true or false to tell you what the action has done. The outputs are also shown in the action logs.
New push option: this lets you tell the action whether to push commit and tags to the repo. The default value is true, so that the default behavior is not changed. (issue #86)
token input: you can now use this instead of setting the GITHUB_TOKEN env variable, which has been deprecated. This input is optional, its default value is the default secrets.GITHUB_TOKEN. You only need to use this if you want the action to run with a PAT. (issue #110)
Deprecated:
GITHUB_TOKEN: the use of this env variable is now deprecated in favor of the token input, you'll start receiving warnings if you keep using it. (issue #110)
[6.0.0] - 2020-12-22
Added:
(BREAKING?) Multiple git commands: support JSON/YAML arrays for the add and remove 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
Added:
Outputs: the action now has 3 outputs (committed, pushed, and tagged) that will be set to either true or false to tell you what the action has done. The outputs are also shown in the action logs.
[5.2.0] - 2020-11-11
Added:
New push option: this lets you tell the action whether to push commit and tags to the repo. The default value is true, so that the default behavior is not changed. (issue #86)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
3 years ago
Bumps EndBug/add-and-commit from v4.4.0 to v6.1.0.
Release notes
Sourced from EndBug/add-and-commit's releases.
... (truncated)
Changelog
Sourced from EndBug/add-and-commit's changelog.
... (truncated)
Commits
a26f63brelease: v6.1.0a71372fci: add test workflow7bdc8af[auto] build: update compiled version5c9f1f7fix: add a couple of debug linesd84d80e[auto] build: update compiled version4d73263fix: add 'token' to Input typeb8f7f0edocs: add Cyberbeni as a contributor (#118)75a30a5feat: deprecate GITHUB_TOKEN env var and use token input instead with default...401756fdocs: update major version tag21ed6afdocs: add issue ref in last changeDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)