Repository navigation
Conversation
|
@olalois is attempting to deploy a commit to the truthixify's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@olalois Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
Auto-retargeted this PR from |
did not intend to target main |
|
Hello, Kindly review please. |
|
The workflow has duplicate pull_request branches keys, unpinned actions, and write permissions on the build job. It also runs build twice. Please fix the YAML, pin every action to a commit SHA, and move PR comments into a least-privilege job. |
|
CI stops because pnpm-lock.yaml has a duplicate key near line 891. The fork run also cannot post the PR comment. Please regenerate the lockfile and move commenting to a separate least-privilege workflow that never executes PR code. |
|
The rebase still leaves a duplicate key in pnpm-lock.yaml near line 891, so all required jobs fail before Lighthouse runs. Regenerate the lockfile from clean develop and rerun CI. |
|
Wave 9 has ended, so this PR is being closed without merging. Thank you for the contribution. |
Summary
Closes #154