Closed glo82145 closed 1 month ago
Fails | |
---|---|
:no_entry_sign: | `node` failed. |
:no_entry_sign: | A version label is required. A maintainer must add one. |
:no_entry_sign: |
Unit tests in the following files did _not_ pass 😔. All tests must pass before this PR can be merged
|
:no_entry_sign: |
No linked issue found. Please link a relevant open issue by adding the text "closes # |
:no_entry_sign: | Missing information in PR. Please fill out the "Description" section. |
Warnings | |
---|---|
:warning: | Found the word "TODO" in the PR description. Just letting you know incase you forgot :) |
Messages | |
---|---|
:book: | DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed). |
:book: | Access a deployed version of this PR [here](https://pr-4285.pwa-venia.com/). Make sure to wait for the "pwa-pull-request-deploy" job to complete. |
ERROR ON TASK: unitTests
Error: Danger had errors running. See message(s) above for more details.
danger-results://tmp/danger-results.json
If your PR is missing information, check against the original template here. At a minimum you must have the section headers from the template and provide some information in each section.
Generated by :no_entry_sign: dangerJS against 0bda90e3a7d4a5514d3463816c97a2505024e42c
run coverage/coveralls
run coveralls-develop
run pr-test
Successfully started codebuild job for pr-test
Description
TODO: Describe your changes in detail here.
Related Issue
Closes #ISSUE_NUMBER.
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist