ci: ensure PR titles follow the Conventional Commits spec

halildurmus commented 1 year ago

Description

I intend to utilize melos for automated versioning and publishing of packages moving forward. To achieve this, we must follow the Conventional Commits specification in our PR titles. This PR introduces a workflow to enforce that requirement.

Additionally, I have disabled merge commits in this repository and will adopt squash merging as our preferred method going forward to maintain a clean commit history (yay!).

@timsneath what do you think about these changes, are you happy with them?

Related Issue

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠️ Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[x] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑️ Chore

timsneath commented 1 year ago

Excellent! I wonder if you want to configure this at the organization level? https://github.blog/changelog/2023-01-10-github-actions-support-for-organization-wide-required-workflows-public-beta/

halildurmus commented 1 year ago

Excellent! I wonder if you want to configure this at the organization level? https://github.blog/changelog/2023-01-10-github-actions-support-for-organization-wide-required-workflows-public-beta/

Awesome! I didn't know about this feature.

Alright, I added the workflow here and configured it for only this repository. Feel free to configure this for other repositories as well.

halildurmus / dartwinrt