Repository files navigation

This project is a fork ofswinton/commit to simply update the NodeJS version to avoid the complaints and deprecations of Github Actions.

✅ Create averified commit with GitHub Actions

This action allows you to create a commit with GitHub Actions. Commits created with this actions will be marked asverified.

In your workflow, to commit a file./myfile, include a step like this:

    -name:Commit fileuses:chromeq/commit@v2.xwith:files:|          myfilecommit-message:Committing ./myfileref:refs/heads/my-branch

chromeq/commit only commits files that have changed.

To commit multiple files in a single commit, pass each file on a newline to thefiles input:

    -name:Commit filesuses:chromeq/commit@v2.xwith:files:|          path/to/myfile1          path/to/myfile2          path/to/myfile3commit-message:Committing filesref:refs/heads/my-branch

Thetoken input is optional.

The following inputs arerequired:

• files: Newline-separated list of files to be committed, relative to root of repository, e.g.

  myfile1
  myfile2
  ...
  myfileN

• commit-message: Commit message to be used, e.g.Add ./myfile
• ref: Fully qualified name of reference to be updated with commit, e.g.refs/heads/production. This referencemust already exist. Defaults to the repository's default branch ref.

This action provides the following outputs:

• commit-sha: SHA of created commit