Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PR Title Validation #7370

Open
sanmarg opened this issue May 17, 2024 · 3 comments
Open

PR Title Validation #7370

sanmarg opened this issue May 17, 2024 · 3 comments

Comments

@sanmarg
Copy link

sanmarg commented May 17, 2024

The purpose of this issue is to ensure that all pull requests (PRs) submitted to our repository follow a consistent and meaningful naming convention. This will improve the readability and maintainability of our project by making it easier to understand the purpose of each PR at a glance. I came across this project and was exploring it and had difficulty in understanding the PR's at glance So I wish to add this. Below is more information for it.

Problem:

Currently, there is no standardized format for PR titles in our repository. This can lead to confusion and difficulty in understanding the intent and scope of changes introduced by each PR. Inconsistent PR titles also make it harder to generate meaningful release notes and track changes over time.

Solution:

To address this issue, we will implement a GitHub Action that automatically checks the titles of PRs against a predefined format. This action will ensure that PR titles follow a specific pattern, making them more informative and standardized.

@ayushrakesh
Copy link

Hello sir , i am much interested to work on this issue.

@ayushrakesh
Copy link

Hello sir, I have raised a PR for this issue. Please review this #7463. It is failing only one check that is documentation check. Can you please help me.

@ayushrakesh
Copy link

Hey @sanmarg , I have raised one PR #7463 , which solves this issue, but it is failing one check which is accessing the link "https://outshift.cisco.com/blog/multi-cluster-monitoring" in docs/getting-started.md ( line 154) gives 500 - Internal Server Error. What should I do now, can you please help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants