You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement a GitHub Actions workflow to automatically validate the titles of pull requests (PRs) when they are opened, edited, reopened, or synchronized. This workflow will ensure that all PR titles adhere to our project's naming conventions, improving clarity and consistency across the repository.
Maintaining a consistent format for PR titles is crucial for effective project management and code review processes. It helps team members quickly understand the purpose and scope of a PR. Automating the validation of PR titles ensures that contributors follow the established naming conventions without manual oversight.
Please assign this issue to me.
It should be implemented because
No response
Additional context
No response
Would you like to work on this issue?
Yes
The text was updated successfully, but these errors were encountered:
Thank you for creating this issue! We'll look into it as soon as possible. Your contributions are highly appreciated! Meanwhile you can show some love to this repo by starring it and following the maintainers : @PranavBarthwal , @surajvast1 & @harshit-sharmaaa 😊
Describe the feature
Implement a GitHub Actions workflow to automatically validate the titles of pull requests (PRs) when they are opened, edited, reopened, or synchronized. This workflow will ensure that all PR titles adhere to our project's naming conventions, improving clarity and consistency across the repository.
Maintaining a consistent format for PR titles is crucial for effective project management and code review processes. It helps team members quickly understand the purpose and scope of a PR. Automating the validation of PR titles ensures that contributors follow the established naming conventions without manual oversight.
Please assign this issue to me.
It should be implemented because
No response
Additional context
No response
Would you like to work on this issue?
Yes
The text was updated successfully, but these errors were encountered: