Closed glo82145 closed 6 months ago
Fails | |
---|---|
:no_entry_sign: | `node` failed. |
:no_entry_sign: | A version label is required. A maintainer must add one. |
: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/Apollo/links/authLink.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-4157.pwa-venia.com/). Make sure to wait for the "pwa-pull-request-deploy" job to complete. |
ERROR ON TASK: prettierCheck
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 4f594e3c253e00983b781284cc3ef0a34f32fcdf
As per our internal process, since there has been no activity on this PR for the last 6 months, I am closing it. Please feel free to reopen if you need any clarification or have any concerns. Thank you.
As per our internal process, since there has been no activity on this PR for the last 6 months, I am closing it. Please feel free to reopen if you need any clarification or have any concerns. Thank you.
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