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.

Sign up for GitHub

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

Jump to bottom

Use labels for filtering #18

Open
mfocko opened this issue Nov 14, 2024 · 0 comments
Open

Use labels for filtering #18

mfocko opened this issue Nov 14, 2024 · 0 comments
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@mfocko
Copy link
Member

mfocko commented Nov 14, 2024

Currently we're filtering the PRs that we validate by using the title of the PR.

For having a more systematic approach of validation, it would be ideal to support labels which allows:

  • easier filtering of the PRs, if we need to retrigger manually to test
  • having an automation-friendly list of tests (they could be parsed for move-stable for example or some CLI status checker)
  • having tests that intentionally fail (e.g. deprecations, or testing specific features tied to the failing result of the external CI (such as OSH))
@mfocko mfocko added area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels Nov 14, 2024
@majamassarini majamassarini moved this from new to backlog in Packit Kanban Board Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mfocko