Add/Remove acceptance-tests-skipped label for PRs

[pmacik]

Signed-off-by: Pavel Macík pavel.macik@gmail.com

Follow-up to: #1150

Changes

This PR:

• Extends the check-skip-acceptance-tests GitHub Action to be able to set or unset the specified label on a PR that can skip (or can't skip resp.)
• Adds a pull_request_target scoped workflow using that action to set or unset acceptance-tests-skipped label

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Docs
  included if any changes are user facing
• Tests
  included if any functionality added or changed. For bugfixes please include tests that can catch regressions
• All acceptance test scenarios included in the PR which verifies a bugfix or a requested feature reported by a non-member are tagged with @external-feedback tag.
• Follows the commit message standard

[codecov]

Codecov Report

Merging #1155 (8b056e8) into master (ace801b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1155   +/-   ##
=======================================
  Coverage   57.84%   57.84%           
=======================================
  Files          31       31           
  Lines        2697     2697           
=======================================
  Hits         1560     1560           
  Misses        976      976           
  Partials      161      161           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ace801b...8b056e8. Read the comment docs.

[pmacik]

Setting a label for PRs wouldn't work with pull_request workflow, but might work with pull_request_target one.

[pedjak]

@pmacik just curious: did you consider using https://github.com/actions/labeler instead of writing the custom action?

[pmacik]

@pmacik just curious: did you consider using https://github.com/actions/labeler instead of writing the custom action?

@pedjak Hey, thanks for that suggestion!

I have considered it, yes. If I only wanted to set labels based on the content, I'd use it. But in this case, setting a label is a follow-up to #1150 where I primarily wanted to selectively skip the acceptance tests based on PR content. For that I considered using the path filtering, however, I couldn't use that because the checks are Required, so I wrote a custom action for that.

This PR extend that custom action by setting the label to inform about the test skipping. Of course, I could use the 'labeler' action for that, but then I'd need to keep and maintain the path filter at 2 places - one in the custom action, which is already in place, and the second in the .github/labeler.yml file.

[dperaza4dustbit]

lgtm

[dperaza4dustbit]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dperaza4dustbit

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 [dperaza4dustbit]

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