avoid using pull_request_target in workflows

[gazarenkov]

Description

Avoid using pull_request_target in workflows in workflows

Building Container Images for Testing

Need to test container images from this PR?

For Maintainers: Comment /build-images to trigger image builds
For Contributors: Ask a maintainer to run /build-images

Images will be built and pushed to Quay with links posted in comments.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nickboldt for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.10.0-pr-2293-f319c6a
2. https://quay.io/rhdh-community/operator-bundle:0.10.0-pr-2293-f319c6a
3. https://quay.io/rhdh-community/operator-catalog:0.10.0-pr-2293-f319c6a

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.10.0-pr-2293-1abb2ef
2. https://quay.io/rhdh-community/operator-bundle:0.10.0-pr-2293-1abb2ef
3. https://quay.io/rhdh-community/operator-catalog:0.10.0-pr-2293-1abb2ef

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.10.0-pr-2293-4db0c82
2. https://quay.io/rhdh-community/operator-bundle:0.10.0-pr-2293-4db0c82
3. https://quay.io/rhdh-community/operator-catalog:0.10.0-pr-2293-4db0c82

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.10.0-pr-2293-68a2ffa
2. https://quay.io/rhdh-community/operator-bundle:0.10.0-pr-2293-68a2ffa
3. https://quay.io/rhdh-community/operator-catalog:0.10.0-pr-2293-68a2ffa

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.10.0-pr-2293-382440b
2. https://quay.io/rhdh-community/operator-bundle:0.10.0-pr-2293-382440b
3. https://quay.io/rhdh-community/operator-catalog:0.10.0-pr-2293-382440b

[rm3l]

/override "PR Publish"
/override "PR Bundle Diff"
/override "PR Validate"

Those were triggered on pull_request_target.

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: PR Bundle Diff, PR Publish, PR Validate

Details

In response to this:

/override "PR Publish"
/override "PR Bundle Diff"
/override "PR Validate"

Those were triggered on pull_request_target.

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.

[rm3l]

/cherry-pick release-1.10
/cherry-pick release-1.9

[openshift-cherrypick-robot]

@rm3l: once the present PR merges, I will cherry-pick it on top of release-1.10, release-1.9 in new PRs and assign them to you.

Details

In response to this:

/cherry-pick release-1.10
/cherry-pick release-1.9

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.

[rm3l]

/override "PR Publish"

Those were triggered on pull_request_target.

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: PR Publish

Details

In response to this:

/override "PR Publish"

Those were triggered on pull_request_target.

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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[openshift-cherrypick-robot]

@rm3l: #2293 failed to apply on top of branch "release-1.10":

Applying: avoid using pull_request_target in workflows
Using index info to reconstruct a base tree...
M	.github/workflows/pr-bundle-diff-checks.yaml
M	.github/workflows/pr-container-build.yaml
M	.github/workflows/pr.yaml
Falling back to patching base and 3-way merge...
Auto-merging .github/workflows/pr-bundle-diff-checks.yaml
CONFLICT (content): Merge conflict in .github/workflows/pr-bundle-diff-checks.yaml
Auto-merging .github/workflows/pr-container-build.yaml
CONFLICT (content): Merge conflict in .github/workflows/pr-container-build.yaml
Auto-merging .github/workflows/pr.yaml
CONFLICT (content): Merge conflict in .github/workflows/pr.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 avoid using pull_request_target in workflows

Details

In response to this:

/cherry-pick release-1.10
/cherry-pick release-1.9

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.

[openshift-cherrypick-robot]

@rm3l: #2293 failed to apply on top of branch "release-1.9":

Applying: avoid using pull_request_target in workflows
Using index info to reconstruct a base tree...
M	.github/workflows/pr-bundle-diff-checks.yaml
M	.github/workflows/pr-container-build.yaml
M	.github/workflows/pr.yaml
Falling back to patching base and 3-way merge...
Auto-merging .github/workflows/pr-bundle-diff-checks.yaml
Auto-merging .github/workflows/pr-container-build.yaml
CONFLICT (content): Merge conflict in .github/workflows/pr-container-build.yaml
Auto-merging .github/workflows/pr.yaml
CONFLICT (content): Merge conflict in .github/workflows/pr.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 avoid using pull_request_target in workflows

Details

In response to this:

/cherry-pick release-1.10
/cherry-pick release-1.9

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.