Skip to content

fix: Ensure router is ready before accessing asPath #85

fix: Ensure router is ready before accessing asPath

fix: Ensure router is ready before accessing asPath #85

Triggered via pull request October 15, 2024 19:27
@l0gicgatel0gicgate
opened #46
Status Failure
Total duration 21s
Artifacts

lint-pr.yml

on: pull_request_target
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
main
Unknown release type "bugfix" found in pull request title "bugfix: Ensure router is ready before accessing asPath". 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
The following actions uses node12 which is deprecated and will be forced to run on node16: amannn/action-semantic-pull-request@v3.1.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
main
The following actions use a deprecated Node.js version and will be forced to run on node20: amannn/action-semantic-pull-request@v3.1.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/