-
Notifications
You must be signed in to change notification settings - Fork 20
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
ci: Validate PR title length instead of commit #1433
Conversation
This repo has @d2iq-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@d2iq-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.For help using mergebot, please refer to the README file here: https://github.com/mesosphere/mergebot/blob/main/README.md |
Pull Request Test Coverage Report for Build 5683851359
💛 - Coveralls |
ec3597b
to
18f41b5
Compare
…e in PR title instead
18f41b5
to
6dd05e4
Compare
* ci(pre-commit): Ignore commit title length in gitlint config, validate in PR title instead * fix(gha): Remove invalid pull_request_target action for pr linter
* ci(pre-commit): Ignore commit title length in gitlint config, validate in PR title instead * fix(gha): Remove invalid pull_request_target action for pr linter
* ci(pre-commit): Ignore commit title length in gitlint config, validate in PR title instead * fix(gha): Remove invalid pull_request_target action for pr linter
…#1492) * fix(kps): Remove duplicate apiserver and unused keepalived scrapeconfig (#1483) * fix(kps): Remove duplicate apiserver scrapeconfig It looks like the KPS chart already defines a servicemonitor which scrapes the apiserver metrics. Our additional scrapeconfig definition is resulting in scraping the same apiserver targets and generating duplicate metrics. We can remove our scrape config and rely on the chart created servicemonitor. * fix(kps): Remove unnecessary keepalived scrape target (cherry picked from commit 90b170c) * ci: Validate PR title length instead of commit (#1433) * ci(pre-commit): Ignore commit title length in gitlint config, validate in PR title instead * fix(gha): Remove invalid pull_request_target action for pr linter * ci(gitlint): Increase body-max-line-length --------- Co-authored-by: Grace Do <xgrace@gmail.com>
…#1491) * fix(kps): Remove duplicate apiserver and unused keepalived scrapeconfig (#1483) * fix(kps): Remove duplicate apiserver scrapeconfig It looks like the KPS chart already defines a servicemonitor which scrapes the apiserver metrics. Our additional scrapeconfig definition is resulting in scraping the same apiserver targets and generating duplicate metrics. We can remove our scrape config and rely on the chart created servicemonitor. * fix(kps): Remove unnecessary keepalived scrape target (cherry picked from commit 90b170c) * ci: Validate PR title length instead of commit (#1433) * ci(pre-commit): Ignore commit title length in gitlint config, validate in PR title instead * fix(gha): Remove invalid pull_request_target action for pr linter * ci(gitlint): Increase body-max-line-length --------- Co-authored-by: Grace Do <xgrace@gmail.com>
…#1493) * fix(kps): Remove duplicate apiserver and unused keepalived scrapeconfig (#1483) * fix(kps): Remove duplicate apiserver scrapeconfig It looks like the KPS chart already defines a servicemonitor which scrapes the apiserver metrics. Our additional scrapeconfig definition is resulting in scraping the same apiserver targets and generating duplicate metrics. We can remove our scrape config and rely on the chart created servicemonitor. * fix(kps): Remove unnecessary keepalived scrape target (cherry picked from commit 90b170c) * ci: Validate PR title length instead of commit (#1433) * ci(pre-commit): Ignore commit title length in gitlint config, validate in PR title instead * fix(gha): Remove invalid pull_request_target action for pr linter * ci(gitlint): Increase body-max-line-length --------- Co-authored-by: Grace Do <xgrace@gmail.com>
What problem does this PR solve?:
Add gitlint rule to ignore commit titles that are too long; since PR titles are used in squash commits, we don't gain anything by limiting the commit messages. Instead, validate that PR titles are not too long.
example of failed run when I updated title to be too long: https://github.com/mesosphere/kommander-applications/actions/runs/5674273398/job/15377493428?pr=1433
Which issue(s) does this PR fix?:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Checklist