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

ci: add OSSAR static analysis workflow #72

Merged
merged 1 commit into from
Apr 2, 2024
Merged

ci: add OSSAR static analysis workflow #72

merged 1 commit into from
Apr 2, 2024

Conversation

castarco
Copy link
Contributor

@castarco castarco commented Apr 2, 2024

Introduce a new static analysis workflow (OSSAR) to check for potential problems.

Signed-off-by: Andres Correa Casablanca <andreu@kindspells.dev>
@castarco castarco added the cicd label Apr 2, 2024
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@castarco castarco merged commit 13e345b into main Apr 2, 2024
8 checks passed
@castarco castarco deleted the ci-ossar branch April 2, 2024 10:17
@castarco
Copy link
Contributor Author

castarco commented Apr 2, 2024

Undone with push --force-with-lease, I made a mistake introducing OSSAR. It seems unmaintained since 2020.

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.

1 participant