Skip to content

fix: The logo readme.md changed to new one #897

fix: The logo readme.md changed to new one

fix: The logo readme.md changed to new one #897

Triggered via pull request May 4, 2024 09:07
@Muniir1Muniir1
edited #298
Status Failure
Total duration 15s
Artifacts

compliance.yml

on: pull_request_target
compliance  /  Semantics
2s
compliance / Semantics
compliance  /  PR Compliance Checks
4s
compliance / PR Compliance Checks
compliance  /  Welcome
0s
compliance / Welcome
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 9 warnings
compliance / Semantics
No release type found in pull request title "logo readme.md changed to new one". Add a prefix to indicate what kind of release this pull request corresponds to (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
compliance / PR Compliance Checks
This PR's title should conform to specification at https://conventionalcommits.org
compliance / Semantics
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: amannn/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
compliance / Semantics
The following actions uses node12 which is deprecated and will be forced to run on node16: amannn/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
compliance / PR Compliance Checks
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: mtfoley/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
compliance / PR Compliance Checks
The following actions uses node12 which is deprecated and will be forced to run on node16: mtfoley/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
compliance / PR Compliance Checks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
compliance / PR Compliance Checks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
compliance / PR Compliance Checks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
compliance / PR Compliance Checks
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
compliance / PR Compliance Checks
PR has main as its head branch, which is discouraged