ci: Lint PR titles with Conventional Commmit standard #1462
+72
−0
Conversation
This file contains hidden or 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
c-warren
requested review from
3vilhamster,
Groxx,
demirkayaender,
dkrotx,
jakobht,
shijiesheng and
taylanisikdemir
as code owners
Signed-off-by: Chris Warren <[email protected]>
c-warren
force-pushed
the
cwarren/cclinter
branch
from
7d7bb7e to
faaf887
Compare
davidporter-id-au
approved these changes
Oct 4, 2025
gazi-yestemirova
pushed a commit
to gazi-yestemirova/cadence-go-client
that referenced
this pull request
Oct 14, 2025
…ow#1462) <!-- Describe what has changed in this PR --> **What changed?** Adds a linter to ensure the conventional commit standard is used for PR titles. <!-- Tell your future self why have you made these changes --> **Why?** See cadence-workflow/cadence@c4b6330 for more details. <!-- How have you verified this change? Tested locally? Added a unit test? Checked in staging env? --> **How did you test it?** In the cadence repo. <!-- Assuming the worst case, what can be broken when deploying this change to production? --> **Potential risks** N/A Signed-off-by: Chris Warren <[email protected]> Signed-off-by: Gaziza Yestemirova <[email protected]>
gazi-yestemirova
added a commit
that referenced
this pull request
Oct 14, 2025
* feat: Introduce FailoverDomain endpoint from cadence-idl Signed-off-by: Gaziza Yestemirova <[email protected]> * fix TestWorkflowExecutionContinuedAsNewEventAttributes Signed-off-by: Gaziza Yestemirova <[email protected]> * ci: Lint PR titles with Conventional Commmit standard (#1462) <!-- Describe what has changed in this PR --> **What changed?** Adds a linter to ensure the conventional commit standard is used for PR titles. <!-- Tell your future self why have you made these changes --> **Why?** See cadence-workflow/cadence@c4b6330 for more details. <!-- How have you verified this change? Tested locally? Added a unit test? Checked in staging env? --> **How did you test it?** In the cadence repo. <!-- Assuming the worst case, what can be broken when deploying this change to production? --> **Potential risks** N/A Signed-off-by: Chris Warren <[email protected]> Signed-off-by: Gaziza Yestemirova <[email protected]> * ci: Allow gpg signed commits to pass DCO checks (#1463) Signed-off-by: Chris Warren <[email protected]> Signed-off-by: Gaziza Yestemirova <[email protected]> * Add endpoints for DomainClient Signed-off-by: Gaziza Yestemirova <[email protected]> * Update clusterName Signed-off-by: Gaziza Yestemirova <[email protected]> * Add another domain to fail over Signed-off-by: Gaziza Yestemirova <[email protected]> --------- Signed-off-by: Gaziza Yestemirova <[email protected]> Signed-off-by: Chris Warren <[email protected]> Co-authored-by: Chris Warren <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changed?
Adds a linter to ensure the conventional commit standard is used for PR titles.
Why?
See cadence-workflow/cadence@c4b6330 for more details.
How did you test it?
In the cadence repo.
Potential risks
N/A