feat(tu-01-06): user authentification #57
Merged
Conversation
This file contains 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
github-actions
bot
added
feature 🚀
✅ Deploy Preview for mad-wizards-tu-tu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
katyastan
changed the title
4 tasks
katyastan
changed the title
Closed
2 tasks
Closed
3 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Title ✨
📍 conforms with the following format:
feat,fix,hotfix,chore,refactor,revert,docs,style,test)tu-01-02, where01- is the sprint number and02- is the issue number)👀 Example:
feat(tu-01-02): descriptionPR Description 🧙♂️
Add:
The system must allow users to sign in using their email and password.
The system should securely authenticate users based on the credentials provided.
The sign-in page should have fields for email and password input.
Acceptance Criteria 1:
User should be authenticated and redirected to the homepage upon entering valid email and password.
Once signed in, the user should not be able to access the Sign In page again until they log out.
NO!!!!!! If an authenticated user tries to access the Sign In page directly via the browser URL, they should be redirected to the Homepage.
After successful authentication each following http-requests must comply with Authorization record
Auto-Review 🤖
Self-Check 🌟