Skip to content

fix - Store the stack for a when creation, so we can know which one isn't complete. 🪧 #188

fix - Store the stack for a when creation, so we can know which one isn't complete. 🪧

fix - Store the stack for a when creation, so we can know which one isn't complete. 🪧 #188

Re-run triggered May 26, 2024 05:03
Status Failure
Total duration 14s
Artifacts

ci.yaml

on: pull_request
semantic_pull_request  /  build
2s
semantic_pull_request / build
Fit to window
Zoom out
Zoom in

Annotations

1 error
semantic_pull_request / build
No release type found in pull request title "Store the stack for a when creation, so we can know which one isn't complete. 🪧". 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