Skip to content

fix: handle path standardization when bucket name not in path #449

fix: handle path standardization when bucket name not in path

fix: handle path standardization when bucket name not in path #449

Triggered via pull request October 16, 2024 13:23
Status Failure
Total duration 16s
Artifacts

conventional-commits.yml

on: pull_request
conventional_commit_title
5s
conventional_commit_title
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
conventional_commit_title
Your pr title doesn't adhere to conventional commits syntax. See more details: {"title":"fix path standardization when bucket name not in path","valid_syntax":"/^(chore|feat|fix|revert|docs|style)(\\([a-z ]+\\))?(!)?: (.)+$/"}
conventional_commit_title
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v5. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
conventional_commit_title
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/github-script@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/