CI's E2E test step has never run — GITHUB_CLIENT_ID/GITHUB_CLIENT_SECRET have never been configured as repository secrets

[chonilius]

.github/workflows/ci.yml's "Run E2E Tests (Conditional)" step:

if [ -z "$GITHUB_CLIENT_ID" ] || [ -z "$GITHUB_CLIENT_SECRET" ]; then
  echo "WARNING: Skipping E2E tests because external GitHub OAuth secrets are not configured..."
else
  npm run test:e2e
fi

gh secret list -R MergeFi/backend returns zero configured repository secrets. This means GITHUB_CLIENT_ID/GITHUB_CLIENT_SECRET have never been set, and this condition has been true on every single CI run since this workflow was introduced — npm run test:e2e has never executed in CI. The step exits 0 either way (the else branch is simply never reached), so this doesn't fail the pipeline or show up as anything other than a warning line buried in a green build — a PR could merge with a fully broken e2e-spec.ts file and CI would report success. See the companion issue for why gating on these secrets isn't even the right condition in the first place — none of the actual e2e specs use them.

[captainjoel2019-bit]

@captainjoel2019-bit has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

‎Hello, I’ve read through the issue description and understand the expected outcome. I’d be happy to take this task on.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @captainjoel2019-bit to this issue.

[bade22brazy]

@bade22brazy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hello maintainer, kindly assign these issues to me. i am sure of handling thenm after careful and thorough review

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bade22brazy to this issue.

[drips-wave]

Congratulations, @bade22brazy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @bade22brazy: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @bade22brazy as part of the Stellar Wave Program's 8th Wave 🥳

😎 @bade22brazy: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.