feat(ci): add workflow for enforcing sementic pr titles #1621
Conversation
WalkthroughThe repository has been updated with a new workflow that ensures pull requests adhere to semantic naming conventions. This addition automates the validation of PR titles, making the project's change management more structured and meaningful. It's a step towards maintaining a cleaner, more organized commit history. Changes
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 (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review Status
Configuration used: CodeRabbit UI
Files selected for processing (1)
- .github/workflows/semantic-pull-request.yml (1 hunks)
Additional comments not posted (3)
.github/workflows/semantic-pull-request.yml (3)
3-8: The trigger events chosen for the workflow are appropriate for the goal of enforcing semantic PR titles.
10-11: The permissions setup for the workflow is correctly scoped to read-only access for pull requests.
13-20: Ensure theamannn/action-semantic-pull-request@v5action is the most stable and secure version available.Verification successful
The verification process has confirmed that
v5.4.0is the latest version of theamannn/action-semantic-pull-requestaction, indicating that the version specified in the workflow (v5) is not the most current. It's recommended to update the action tov5.4.0for the best stability and security. Regarding security advisories, the GitHub API did not return any open advisories for the repository, either due to the absence of advisories or because such information might not be publicly accessible through the API. Based on the information available, it's advisable to update to the latest version of the action.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check for the latest version of the action gh api -X GET /repos/amannn/action-semantic-pull-request/releases/latest | jq -r '.tag_name' # Check for any open security advisories gh api -X GET /repos/amannn/action-semantic-pull-request/security/advisories | jq '.'Length of output: 294
<!-- Please read and fill out this form before submitting your PR. Please make sure you have reviewed our contributors guide before submitting your first PR. --> ## Overview <!-- Please provide an explanation of the PR, including the appropriate context, background, goal, and rationale. If there is an issue with this information, please provide a tl;dr and link the issue. --> Create streamlined PR template. Remove checklist and add link to semver commits because of #1621 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Documentation** - Introduced a pull request template to streamline contributions and improve the quality of submissions. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Overview
Adds workflow to enforce semantic PR titles.
NOTE: this was copy pasted from celestia-app
Summary by CodeRabbit