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

fips-v1.7.1 #3

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

fips-v1.7.1 #3

wants to merge 1 commit into from

Conversation

ramandeepsharma
Copy link

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
  • The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
  • I've signed my commits with DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My builds are green. Try syncing with master if they are not.
  • My organization is added to USERS.md.

@acquia-devops-ci-cd-pipeline-4

⚠️ Orca Scan Vulnerabilities

status URL
CVEs found with status: WARNING https://cloudbees.ais.acquia.io/devops-pipeline-4-jenkins/blue/organizations/jenkins/KCS-argo-rollouts-PIPELINE/detail/PR-3/1/

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.

1 participant