Skip to content

fix: Use / in relative path for Windows #1533

fix: Use / in relative path for Windows

fix: Use / in relative path for Windows #1533

Triggered via pull request November 8, 2024 06:48
@AlexV525AlexV525
opened #788
Status Failure
Total duration 13s
Artifacts

pr_title.yaml

on: pull_request_target
Validate PR title
2s
Validate PR title
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Validate PR title
No release type found in pull request title "🐛 Use `/` in relative path for Windows". 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
Validate PR title
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/
Validate PR title
The following actions use a deprecated Node.js version and will be forced to run on node20: amannn/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/