ci: Validate PR title #170
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ahmed Moussa <[email protected]>
hamada147
requested review from
elribonazo,
goncalo-frade-iohk,
yshyn-iohk,
curtis-h,
cristianIOHK and
amagyar-iohk
as code owners
Code Coverage
|
goncalo-frade-iohk
approved these changes
May 31, 2024
todorkoleviohk
added a commit
that referenced
this pull request
Jun 2, 2024
…ter) ci: Validate PR title (#170) Signed-off-by: Ahmed Moussa <[email protected]> syncing with main and applying the change there too squashing squashing
|
🎉 This PR is included in version 1.3.5 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Add PR title validation to be in line with conventional commits.
Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist: