Skip to content

ci: do not scan the tests for security issues #926

ci: do not scan the tests for security issues

ci: do not scan the tests for security issues #926

Triggered via pull request March 19, 2024 15:31
@insumityinsumity
synchronize #1715
Status Failure
Total duration 18s
Artifacts

lint-pr.yml

on: pull_request_target
Fit to window
Zoom out
Zoom in

Annotations

2 errors
main
No release type found in pull request title "first commit". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - feat: A new feature - fix: A bug fix - docs: Documentation only changes - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) - refactor: A code change that neither fixes a bug nor adds a feature - perf: A code change that improves performance - test: Adding missing tests or correcting existing tests - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) - chore: Other changes that don't modify src or test files - revert: Reverts a previous commit
main
Resource not accessible by integration