-
Notifications
You must be signed in to change notification settings - Fork 1
add conventional commit message for github. #4
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Abhiraj Roy <157954129+iconized@users.noreply.github.com>
…pull Signed-off-by: Abhiraj Roy <157954129+iconized@users.noreply.github.com>
WalkthroughThe recent updates introduce a GitHub Actions workflow to enforce Commitizen conventions on commit messages for the Changes
Sequence Diagram(s) (Beta)sequenceDiagram
actor Developer
participant GitHub Actions
participant GitHub Repository
Developer->>GitHub Repository: Push/Pull Request to master
GitHub Actions->>GitHub Repository: Trigger workflow
GitHub Actions->>GitHub Actions: Checkout repository
GitHub Actions->>GitHub Actions: Install Node.js
GitHub Actions->>GitHub Actions: Install Commitizen
GitHub Actions->>GitHub Actions: Verify commit messages
GitHub Actions-->>Developer: Commit message verification result
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- .github/workflows/commitizen.yml (1 hunks)
- iconfig.sh (1 hunks)
Files skipped from review due to trivial changes (1)
- iconfig.sh
Additional comments not posted (3)
.github/workflows/commitizen.yml (3)
3-9
: Trigger configuration looks good and correctly targets themaster
branch for both push and pull_request events.
11-14
: Job configuration is appropriate and well-defined.
16-26
: Steps for checking out the repository and installing Node.js and Commitizen are correctly configured.
No description provided.