Releases: motlin/forbid-merge-commits-action
Release list
v1.0.8
What's Changed
- Fix local test by adding mock PR event payload and yamllint config by @motlin in #38
- Sync foundational files from project-template by @motlin in #40
- Bump actions/checkout from v4 to v6 to drop Node 20 dependency. by @motlin in #41
- Simplify the .gitattributes file by removing the CRLF and linguist rules. by @motlin in #42
Full Changelog: v1.0.7...v1.0.8
v1.0.7
v1.0.6
v1.0.5
What's Changed
- Add configuration
fail-on-merge-commitsto allow the action to either warn or fail. by @motlin in #32
Full Changelog: v1.0.4...v1.0.5
v1.0.4
What's Changed
- Improve error message by including the event type when the action fails. by @motlin in #31
- Improve README.md
Full Changelog: v1.0.3...v1.0.4
v1.0.3
What's Changed
- Upgrade actions/checkout from v3 to v4. by @motlin in #27
- Rename workflow job from check-merge-commits to forbid-merge-commits. by @motlin in #28
Full Changelog: v1.0.2...v1.0.3
v1.0.2
v1.0.1
What's Changed
Full Changelog: v1.0.0...v1.0.1
v1.0.0
This Action fails on Pull Requests that include merge commits.
This rule is designed to prevent developers from merging the default branch into their branch as a way of making it up-to-date. This creates foxtrot commits and confusing git log graphs.
This rule is also designed to prevent using GitHub's "Update Branch" button, which merges the base branch into the source branch. Instead, use the pull-down "Rebase Branch" button which rebases the source branch onto the base branch. This is a common problem if "Always suggest updating pull request branches" is enabled, because "Update Branch" is the default choice in the pull-down and it cannot be disabled or changed.
Full Changelog: https://github.com/motlin/forbid-merge-commits-action/commits/v1.0.0