Skip to content

Fixing gosec workflow error #147

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.

Sign up for GitHub

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

Jump to bottom
Merged
Mzack9999 merged 1 commit into from
Jul 27, 2022
Merged

Fixing gosec workflow error #147

Mzack9999 merged 1 commit into from
Jul 27, 2022

Conversation

@Mzack9999
Copy link
Member

@Mzack9999 Mzack9999 commented Jul 27, 2022 •
edited
Loading

Proposed changes

Fixes https://github.com/projectdiscovery/proxify/runs/7486075969?check_suite_focus=true

Checklist

  • Pull request is created against the dev branch
  • All checks passed (lint, unit/integration/regression tests etc.) with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

@Mzack9999 Mzack9999 added the Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity. label Jul 27, 2022
@Mzack9999 Mzack9999 self-assigned this Jul 27, 2022
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 27, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@Mzack9999 Mzack9999 merged commit e665f52 into dev Jul 27, 2022
@Mzack9999 Mzack9999 deleted the maintenance-gosec branch July 27, 2022 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@Mzack9999 Mzack9999

Labels

Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Mzack9999