pwa-studio-bot
commented
8 months ago | Fails | |
|---|---|
| :no_entry_sign: | `node` failed. |
| :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. |
| :no_entry_sign: | The following file(s) were not formatted with **prettier**. Make sure to execute `yarn run prettier` locally prior to committing. ``` packages/peregrine/lib/talons/SignIn/useSignIn.js ``` |
| 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-4226.pwa-venia.com/). Make sure to wait for the "pwa-pull-request-deploy" job to complete. |
Log
ERROR ON TASK: prettierCheck
Error: Danger had errors running. See message(s) above for more details.
danger-results://tmp/danger-results.jsonIf 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 8b723a1724354a016ea819ca286166a6ea4a206f
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