• Force behavior updated: force: true now uses git push --force (breaking change)
• New parameter: force_with_lease for safer force pushing with --force-with-lease
• Amend improvements: Can now combine amend: true with commit_message to change commit messages

A powerful GitHub Action for automatically committing and pushing changes back to your repository. Perfect for automation workflows and integrates seamlessly with devops-infra/action-pull-request.

• Docker Hub: devopsinfra/action-commit-push:latest
• GitHub Packages: ghcr.io/devops-infra/action-commit-push/action-commit-push:latest

• 📝 Custom commit messages: Add custom prefixes and messages to commits
• 🌿 Branch management: Create new branches automatically with optional timestamps
• ⏰ Timestamp support: Add timestamps to branch names for cron-based updates
• 🔄 Integration-ready: Works seamlessly with other DevOps workflows
• 💪 Force push options: Support for --force and --force-with-lease when needed
• 🔀 Pull request integration: Perfect companion for automated PR workflows

 - name: Run the Action uses: devops-infra/action-commit-push@master with: github_token: "${{ secrets.GITHUB_TOKEN }}" add_timestamp: true commit_prefix: "[AUTO]" commit_message: "Automatic commit" force: false force_with_lease: false target_branch: update/version

Commit and push changes to the currently checked out branch.

name: Push changes on: push jobs: change-and-push: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v4 - name: Change something run: |  find . -type f -name "*.md" -print0 | xargs -0 sed -i "s/foo/bar/g"  - name: Commit and push changes uses: devops-infra/action-commit-push@master with: github_token: ${{ secrets.GITHUB_TOKEN }} commit_message: "Replace foo with bar"

Commit and push changes to a new branch and create a pull request using devops-infra/action-pull-request.

name: Push changes and create PR on: push jobs: change-and-push: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v4 - name: Change something run: |  find . -type f -name "*.md" -print0 | xargs -0 sed -i "s/foo/bar/g"  - name: Commit and push changes uses: devops-infra/action-commit-push@master with: github_token: ${{ secrets.GITHUB_TOKEN }} commit_prefix: "[AUTO-COMMIT] " commit_message: "Replace foo with bar" - name: Create pull request uses: devops-infra/action-pull-request@master with: github_token: ${{ secrets.GITHUB_TOKEN }} body: "**Automated pull request**<br><br>Replaced foo with bar" title: ${{ github.event.commits[0].message }}

When you need to amend the previous commit and force push (useful for fixing commit messages or adding forgotten changes).

name: Amend and force push on: workflow_dispatch: inputs: new_commit_message: description: 'New commit message' required: true default: 'Updated commit message' jobs: amend-commit: runs-on: ubuntu-latest steps: - name: Checkout repository with full history uses: actions/checkout@v4 with: fetch-depth: 0 # Required for force_with_lease - name: Make some changes run: |  echo "Additional content" >> README.md  - name: Amend and force push with lease uses: devops-infra/action-commit-push@master with: github_token: ${{ secrets.GITHUB_TOKEN }} commit_message: ${{ github.event.inputs.new_commit_message }} amend: true force_with_lease: true # Safer force push option

When using amend: true, you have several options for handling the commit message:

1. Change the commit message: Set commit_message to provide a new message

   - uses: devops-infra/action-commit-push@master with: github_token: ${{ secrets.GITHUB_TOKEN }} commit_message: "Fixed typo in documentation" amend: true force_with_lease: true

2. Keep existing message: Set no_edit: true to keep the original commit message

   - uses: devops-infra/action-commit-push@master with: github_token: ${{ secrets.GITHUB_TOKEN }} amend: true no_edit: true force_with_lease: true

3. Default behavior: If neither is set, uses "Files changed:" with file list (when files are modified)

💡 Note: Amending works even without file changes - useful for just changing commit messages!

This action follows a release-based Docker image deployment strategy:

• Development branches: Only build and test Docker images (no push to Docker Hub)
• Test branches (test/*): Build and push Docker images with test- prefix for integration testing
• Master branch: Only build and test Docker images (no push to Docker Hub)
• Releases: Docker images are built and pushed to Docker Hub only when a new GitHub release is created
• Weekly builds: Automated test builds run weekly and push test images

1. Create a new GitHub release with a version tag (e.g., v0.11.0)
2. The release workflow automatically:
   • Builds multi-architecture Docker images (amd64, arm64)
   • Pushes images to Docker Hub with the release version tag
   • Updates the action.yml file to reference the new Docker image version
   • Updates Docker Hub description

For testing changes before creating a release:

1. Create a branch starting with test/ (e.g., test/new-feature)
2. Push your changes to this branch
3. The workflow automatically builds and pushes Docker images with test- prefix
4. Use the test image in other workflows: devopsinfra/action-commit-push:test-latest

This ensures that:

• ✅ Master branch merges don't accidentally publish untested images
• ✅ Test branches provide safe testing environments
• ✅ Only stable, released versions are available on Docker Hub
• ✅ Users can pin to specific, tested versions
• ✅ Development and testing don't interfere with production images

This action provides two force push options for different scenarios:

• Uses git push --force-with-lease
• Safer option that checks if someone else has pushed changes to the remote branch
• Prevents accidentally overwriting other people's work
• Required: Set fetch-depth: 0 in your actions/checkout step
• Use case: Amending commits, rebasing, or other history modifications

• Uses git push --force
• Potentially dangerous as it will overwrite remote changes unconditionally
• No safety checks - will overwrite any remote changes
• Use case: Only when you're absolutely certain you want to overwrite remote changes

⚠️ Important: Never use both options simultaneously. force_with_lease takes precedence if both are set to true.

Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.

This project is licensed under the MIT License - see the LICENSE file for details.

• devops-infra/action-pull-request - Create pull requests automatically
• devops-infra/.github - Shared GitHub configuration and templates

If you have any questions or need help, please:

• 📝 Create an issue
• 💬 Start a discussion
• 🌟 Star this repository if you find it useful!