Skip to content

Conversation

@IchordeDionysos
Copy link
Contributor

@IchordeDionysos IchordeDionysos commented Nov 11, 2025

Rules:

  • Follows conventional commits (with allowed change types)
  • Uses uppercase in subject
  • Puts Jira issues in brackets

Ensure that commits follow the format:

feat: Update dependencies (SC-123)
feat(packageA): Update dependencies (SC-123)
feat: Update dependencies

And block the following PR/commit names:

Update dependencies
feat: SC-123 Update dependencies
feat: update dependencies (SC-123)
feat: Update dependencies SC-123
feat: SC-123-update-dependencies
feat: update-dependencies

@coderabbitai
Copy link

coderabbitai bot commented Nov 11, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch D/conventional-commit-lint-workflow

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@IchordeDionysos
Copy link
Contributor Author

@coderabbitai review

@coderabbitai
Copy link

coderabbitai bot commented Nov 11, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@IchordeDionysos IchordeDionysos changed the title feat: Conventional commit linter for standardised commits/PRs feat : Conventional commit linter for standardised commits/PRs Nov 11, 2025
@IchordeDionysos IchordeDionysos changed the title feat : Conventional commit linter for standardised commits/PRs feat: conventional commit linter for standardised commits/PRs Nov 11, 2025
@IchordeDionysos IchordeDionysos changed the title feat: conventional commit linter for standardised commits/PRs feat: Conventional commit linter for standardised commits/PRs SC-123 Nov 11, 2025
@IchordeDionysos IchordeDionysos changed the title feat: Conventional commit linter for standardised commits/PRs SC-123 feat: Conventional commit linter for standardised commits/PRs (SC-123) Nov 11, 2025
@IchordeDionysos IchordeDionysos changed the title feat: Conventional commit linter for standardised commits/PRs (SC-123) feat: Conventional commit linter for standardised commits/PRs Nov 11, 2025
Copy link

@richard-webb-dev richard-webb-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd be happy with this. You should get more reviews though
i think it could be a bit more lenient too - capitalized first letter!?

If you can find a way to give warnings instead of errors on missing tickets, or a way to implement per repo, you'll be able to merge this much quicker

@IchordeDionysos
Copy link
Contributor Author

It doesn't error on missing tickets :)

@IchordeDionysos IchordeDionysos merged commit 387b3bd into main Nov 28, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants