Move priority/backlog to global label definition

[anishbista60]

What this PR does / why we need it:

• Move priority/backlog to global label definition adjacent to priority/critical-urgent

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3654

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

None

[kubevirt-bot]

Hi @anishbista60. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[anishbista60]

@dhiller Request for review ?

[dhiller]

@dhiller Request for review ?

You mean

/cc @dhiller

[dhiller]

@anishbista60 the file you have changed is auto-generated, therefore changing it will have no effect on the label definitions.

Editing our GitHub labels is done by editing the labels.yaml - similarly to adding a label 2 - thus we need to move the label definition of priority/backlog 3 to somewhere below the yaml path .default.labels (best would be to place it adjacent to the other priority label.

Afterwards you need to run make update-labels, which will update the labels.md file.

Please do all this in one commit, so we have the changes grouped together nicely.

Thank you for looking into this!

[dhiller]

@anishbista60 I have update the issue description also - hope the task is more clear now. Sorry for the confusion.

[anishbista60]

@dhiller Thank you

[anishbista60]

@anishbista60 the file you have changed is auto-generated, therefore changing it will have no effect on the label definitions.

Editing our GitHub labels is done by editing the labels.yaml - similarly to adding a label 2 - thus we need to move the label definition of priority/backlog 3 to somewhere below the yaml path .default.labels (best would be to place it adjacent to the other priority label.

Afterwards you need to run make update-labels, which will update the labels.md file.

Please do all this in one commit, so we have the changes grouped together nicely.

Thank you for looking into this!

Thanks for great explanation, made it so easy .
Now, every thing done. Please check.

[dhiller]

/approve

Thank you!

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dhiller]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubevirt-bot]

@anishbista60: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-project-infra-prow-deploy-test	22c93f1	link	true	/test pull-project-infra-prow-deploy-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[anishbista60]

@dhiller pull-project-infra-prow-deploy-test failing

[anishbista60]

@brianmcarey could you please look into ? unable to get the exact reason