Skip to content
git-commit

GitHub Action

Verified Git Commit

v2.0.0 Latest version

Verified Git Commit

git-commit

Verified Git Commit

GitHub Action to create verified commits

Installation

Copy and paste the following snippet into your .yml file.

              

- name: Verified Git Commit

uses: ChromeQ/commit@v2.0.0

Learn more about this action in ChromeQ/commit

Choose a version

Fork

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

image

Commit

✅ Create a verified commit with GitHub Actions

code style: prettier

About

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

image

Usage

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

    - name: Commit file
      uses: chromeq/commit@v2.x
      with:
        files: |
          myfile
        commit-message: Committing ./myfile
        ref: 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 the files input:

    - name: Commit files
      uses: chromeq/commit@v2.x
      with:
        files: |
          path/to/myfile1
          path/to/myfile2
          path/to/myfile3
        commit-message: Committing files
        ref: refs/heads/my-branch

Inputs

The token input is optional.

The following inputs are required:

  • 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 reference must already exist. Defaults to the repository's default branch ref.

Outputs

This action provides the following outputs:

  • commit-sha: SHA of created commit