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

fix(zap_scan): Label issues correctly #204

Merged
merged 2 commits into from
Nov 10, 2023
Merged

Conversation

jeremyckahn
Copy link
Owner

This PR is a followup to #199. It attempts to fix the labeling of issues created by the ZAProxy scan.

It can only be tested after merging.

Copy link

vercel bot commented Nov 10, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
chitchatter ✅ Ready (Inspect) Visit Preview Nov 10, 2023 6:02pm

@jeremyckahn jeremyckahn merged commit 5317d6f into develop Nov 10, 2023
5 checks passed
@jeremyckahn jeremyckahn deleted the fix/zap-scan-ref branch November 10, 2023 18:03
steps:
- name: Check if issue title starts with "Security Report -"
id: check_title
run: echo "::set-output name=startsWithSecurityReport::$(echo ${{ github.event.issue.title }} | grep -q '^Security Report -' && echo true || echo false)"

Check failure

Code scanning / CodeQL

Expression injection in Actions Critical

Potential injection from the ${{{{ github.event.issue.title }}}}, which may be controlled by an external user.
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.

None yet

1 participant