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

gha: add pr-validation GH action #1384

Merged
merged 1 commit into from
Aug 28, 2023
Merged

gha: add pr-validation GH action #1384

merged 1 commit into from
Aug 28, 2023

Conversation

kkourt
Copy link
Contributor

@kkourt kkourt commented Aug 23, 2023

This action validates PRs based on labels.
It blocks PRs that have a dont-merge/* label, and blocks PRs that do not have a release-note/* labe.

This action validates PRs based on labels.
It blocks PRs that have a dont-merge/* label, and blocks PRs that do not
have a release-note/* labe.

Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
@kkourt kkourt added the release-note/ci This PR makes changes to the CI. label Aug 23, 2023
@mtardy
Copy link
Member

mtardy commented Aug 25, 2023

and blocks PRs that do not have a release-note/* label.

Do you think all PRs should be labeled with some sort of release-note label?

@kkourt
Copy link
Contributor Author

kkourt commented Aug 25, 2023

and blocks PRs that do not have a release-note/* label.

Do you think all PRs should be labeled with some sort of release-note label?

yes. that's the point of this PR. It can be release-note/misc but it would be nice to force folk to think about this.

Copy link
Contributor

@michi-covalent michi-covalent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i love dont-merge labels 🥰

@kkourt kkourt merged commit c6abdb8 into main Aug 28, 2023
25 of 26 checks passed
@kkourt kkourt deleted the pr/kkourt/pr-validation branch August 28, 2023 07:10
@mtardy
Copy link
Member

mtardy commented Sep 4, 2023

Could we maybe ignore bot-related PR for those validations? Not sure we need release notes for deps bumps, for example #1397. I see two things:

  • bots can add an appropriate label
  • we can ignore PRs from bots in the validation workflow

@michi-covalent
Copy link
Contributor

we should just configure renovate to add a label, maybe release-note/dependency or something. then we we can group these PRs in the release note, or even exclude them if we decide not to include them in the release note 🥰

mtardy added a commit that referenced this pull request Sep 5, 2023
See #1384 (comment) and #1384 (comment).

Signed-off-by: Mahé <mahe.tardy@gmail.com>
mtardy added a commit that referenced this pull request Sep 5, 2023
See #1384 (comment) and
#1384 (comment).

Signed-off-by: Mahé <mahe.tardy@gmail.com>
mtardy added a commit that referenced this pull request Sep 6, 2023
See #1384 (comment) and
#1384 (comment).

Signed-off-by: Mahé <mahe.tardy@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants