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

Backport of Mw/add backport checker into release/1.0.x #1984

Conversation

hc-github-team-consul-core

Backport

This PR is auto-generated from #1982 to be assessed for backporting due to the inclusion of the label backport/1.0.x.

The below text is copied from the body of the original PR.


Changes proposed in this PR:

  • Add a pipeline check for backport labels. This will ensure that developers must either add a backport label or deliberately specify that this pr does not require backporting with the pr/no-backport label.
  • This check simply checks for the presence of a label matching backport/*. It is up to the developer to add the right backport labels as appropriate for a given PR.

How I've tested this PR:

No Backport label and no pr/no-backport
image

With backport label
image

With pr/no-backport label
image

How I expect reviewers to test this PR:

Checklist:

  • Tests added
  • CHANGELOG entry added

    HashiCorp engineers only, community PRs should not add a changelog entry.
    Entries should use present tense (e.g. Add support for...)


Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/mw/add-backport-checker/vigorously-notable-caiman branch from 01810fb to 01b910e Compare March 3, 2023 21:03
@hc-github-team-consul-core hc-github-team-consul-core merged commit e801667 into release/1.0.x Mar 3, 2023
@hc-github-team-consul-core hc-github-team-consul-core deleted the backport/mw/add-backport-checker/vigorously-notable-caiman branch March 3, 2023 21:03
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

Successfully merging this pull request may close these issues.

2 participants