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

Prow CI should only run against PRs that touch Pelorus code #1076

Open
1 task done
mateusoliveira43 opened this issue Sep 29, 2023 · 0 comments
Open
1 task done

Prow CI should only run against PRs that touch Pelorus code #1076

mateusoliveira43 opened this issue Sep 29, 2023 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@mateusoliveira43
Copy link
Collaborator

OpenShift version

Not related to OpenShift

Problem description

Today, Prow CI jobs runs against all PRs. It should only run against PRs related to Pelorus code, i.e.:

  • exporters folder
  • charts folder
  • pelorus-operator folder

Example configuration on how to achieve this:

Steps to reproduce

Not aplicable.

Current behavior

Prow CI jobs run against all PRs.

Expected behavior

Prow CI jobs run only on necessary PRs.

Code of Conduct

  • I agree to follow Pelorus's Code of Conduct
@mateusoliveira43 mateusoliveira43 added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant