Repository navigation
chore: Document a dev test account for local checks - #257
Merged
Merged
Conversation
Changes: - Add DEV_ACCOUNT_EMAIL and DEV_ACCOUNT_PASSWORD to frontend/.env.local.example, with how to create the account Agents and manual checks need a logged-in account to compare screens; the variables are tooling only and the app never reads them, as in Project01.
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 34 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ Deploy Preview for disscount ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Visual and functional checks of logged-in screens need an account. This documents a throwaway dev account the same way Project01 does, so agents and manual checks can sign in locally without anyone's real credentials.
Changes
frontend/.env.local.example:DEV_ACCOUNT_EMAILandDEV_ACCOUNT_PASSWORD, tooling only (the app never reads them), with how to create the account: sign up through/api/auth/sign-up/email, then mark it verified in that databaseTesting
Risks
None at runtime; documentation of local tooling only.