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 ci: update the security-scanner gha token into release/1.5.x #4332

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

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

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@dduzgun-security
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-k8s/merges: 409 Merge conflict []

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


Changes proposed in this PR

Using the org level secret instead of the repository one and removing conditional check to use paths-ignore.

How I've tested this PR

If the security scan passes, we are good.

How I expect reviewers to test this PR

If the security scan passes, we are good.

Checklist


Overview of commits

Copy link

hashicorp-cla-app bot commented Sep 17, 2024

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


1 out of 2 committers have signed the CLA.

  • dduzgun-security
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@dduzgun-security dduzgun-security marked this pull request as ready for review September 17, 2024 18:37
@dduzgun-security dduzgun-security enabled auto-merge (squash) September 17, 2024 18:37
@dduzgun-security dduzgun-security merged commit b1d8830 into release/1.5.x Sep 26, 2024
45 of 49 checks passed
@dduzgun-security dduzgun-security deleted the backport/ci/update-security-scanner-token/randomly-wondrous-stork branch September 26, 2024 19:12
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