approvals / ApprovalTests.cpp

Native ApprovalTests for C++ on Linux, Mac and Windows
https://approvaltestscpp.readthedocs.io/en/latest/
Apache License 2.0
310 stars 50 forks source link

Bump EndBug/add-and-commit from 4 to 9 #198

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps EndBug/add-and-commit from 4 to 9.

Release notes

Sourced from EndBug/add-and-commit's releases.

v9.0.0

Changed:

  • [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)

Added:

  • tag_push input: you can now set the arguments of the git push --tags command.
  • tag_pushed output: whether the action pushed tags.

v8.0.2

Fixed:

  • The commit input is now properly listed in the README. (#360)

v8.0.1

Fixed:

  • Fixed a bug that prevented the --allow-empty flag from being used for the commit input. (#352)
  • Fixed README and CHANGELOG docs for the pull input, that were still showing the option to use NO-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)

v8.0.0

Fixed:

  • [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-added new_branch input. For more info, check commit 6fdb34e.

Removed:

  • [BREAKING] The signoff input has been removed, use commit instead. (#331)
  • [BREAKING] The pull_strategy input has been removed, use pull instead.
  • [BREAKING] The branch and branch_mode inputs have been removed, check commit 6fdb34e for more info.
  • [BREAKING] The pull input doesn't support NO-PULL anymore: if you don't want the action to pull, simply remove the input, as it's the default behavior now.

Added:

  • Added the commit input, that allows you to change the arguments for the git commit command. (#331)
  • Added the new_branch input. (6fdb34e)
  • Added the commit_long_sha output. (#349)

v7.5.0

Added:

  • 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)

v7.4.0

Added:

  • Added pull input: you can use it to change the arguments of the git pull command (#294)

... (truncated)

Changelog

Sourced from EndBug/add-and-commit's changelog.

[7.1.1] - 2021-04-04

Fixed:

  • Git args parsing has been improved, and now handles spaces correctly (issue #154)

[7.1.0] - 2021-03-03

Added:

  • pull_strategy: you can use 'NO-PULL' to prevent the action from pulling from the remote at all.

[7.0.0] - 2021-01-16

Changed:

  • [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: username@users.noreply.github.com
  • [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

Added:

  • push input: allow for custom git push arguments to be used, more info in the README. (issue #100)

[6.1.0] - 2020-12-22

Added:

  • 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

... (truncated)

Commits
  • 998652d docs: update changelog
  • 66ecef4 9.0.1
  • cbc4f17 fix: correct typo in error
  • ff41bd8 docs: add onedr0p as a contributor for bug (#413)
  • f01349f docs: add AvivPeledTalon as a contributor for bug (#412)
  • 0d52df4 fix: re-stage files after pulling (#411)
  • 9fc8e26 chore(deps-dev): bump typescript from 4.7.3 to 4.7.4 (#409)
  • b7a37a1 chore(deps): bump @​actions/core from 1.8.2 to 1.9.0 (#408)
  • d93b31c chore(deps-dev): bump prettier from 2.6.2 to 2.7.1 (#407)
  • d56de92 chore: bump simple-git
  • Additional commits viewable in compare view


Dependabot compatibility score

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)