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(scanner): Update scorecard and secret scanner actions #456

Merged
merged 7 commits into from
Jul 5, 2024

Conversation

dhfherna
Copy link
Contributor

Description

Update Github actions configuration files for Scorecards and secret scanner using StepSecurity tool

Category

  • Feature
  • Fix
  • Ci / Docs

Checklist

  • The pull request is complete according to the guide of contributing
  • Automated tests are written
  • The documentation is up-to-date
  • The pull request has a descriptive title that describes what has changed, and provides enough context for the changelog
  • If the pull request has a new driven-adpater or entry-point, you should add it to RADME.md and sh_generate_project.sh files for generated code tests.
  • If the pull request has changed structural files, you have implemented an UpgradeAction according to the guide
  • If the pull request has a new Gradle Task, you should add Analytics according to the guide

Copy link
Contributor

@juancgalvis juancgalvis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@juancgalvis juancgalvis changed the title Update scorecard and secret scanner actions fix(scanner): Update scorecard and secret scanner actions Jun 17, 2024
@dhfherna dhfherna merged commit d78fb25 into bancolombia:master Jul 5, 2024
4 of 6 checks passed
Copy link
Contributor

🎉 This PR is included in version 3.17.13 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants