release!: v3

[avidal]

commit-headless v3.0.0

This PR contains breaking changes to the CLI and action interfaces, along with new features.

Breaking Changes

push command

The push command no longer accepts commit arguments. It now automatically determines which local commits need to be pushed by comparing local HEAD with the remote branch HEAD.

Before:

commit-headless push -T owner/repo --branch feature <commit1> <commit2>

After:

commit-headless push -T owner/repo --branch feature

The commits action input has been removed.

commit command

The commit command no longer accepts file arguments. It now reads from the git staging area, similar to git commit.

Before:

commit-headless commit -T owner/repo --branch feature -m "message" file1.txt file2.txt

After:

git add file1.txt file2.txt
commit-headless commit -T owner/repo --branch feature -m "message"

The files action input has been removed.

New Features

--force for commit and push commands

When --force is set, --head-sha is used directly as the parent of the first pushed commit, bypassing the remote HEAD safety check. The branch ref is force-updated even if the push is not a fast-forward. This is useful for, e.g., pushing rebased commits.

Without this, there is no way for commit-headless to force push.

replay command

New command to replay existing remote commits as signed commits. Useful when an action or bot creates unsigned commits that you want to replace with signed versions.

commit-headless replay -T owner/repo --branch feature --since abc123

The command fetches the remote branch, extracts commits since the specified base, recreates them as signed commits, and force-updates the branch ref.

Action usage:

- uses: DataDog/commit-headless@action/v3.0.0
  with:
    branch: ${{ github.ref_name }}
    since: ${{ github.sha }}
    command: replay

File mode preservation

File modes (such as the executable bit) are now preserved when pushing commits. Previously all files were created with mode 100644.

GitHub Actions logging

When running in GitHub Actions, output now uses workflow commands:

• Commit operations are grouped for cleaner logs
• Success/failure notices appear in the workflow summary
• Warnings and errors use appropriate annotation levels

Internal Changes

• Switched from GraphQL API to REST API
• Added CI test workflow for integration testing on pull requests
• Release workflow now verifies binaries on both amd64 and arm64 before releasing