Skip to content

feat:New sing in UI #589

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 15 commits into from
Closed

feat:New sing in UI #589

wants to merge 15 commits into from

Conversation

Esther-Lita
Copy link
Collaborator

@Esther-Lita Esther-Lita commented Jul 22, 2024

Screenshot 2024-07-22 at 17 56 40 Screenshot 2024-07-22 at 17 57 29

What does this PR do?

New Login UI, also Buttons align center on new image upload

Fixes # (issue)

If there is not an issue for this, please create one first. This is used to tracking purposes and also helps use understand why this PR exists

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist

Required

  • Read Contributing Guide
  • Self-reviewed my own code
  • Tested my code in a local environment
  • Commented on my code in hard-to-understand areas
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the UnInbox Docs if changes were necessary

Added the rest of the logic to handle the 2FA
@BlankParticle BlankParticle mentioned this pull request Jul 23, 2024
16 tasks
@BlankParticle
Copy link
Member

Closed due to issues described in #592

BlankParticle added a commit that referenced this pull request Jul 23, 2024
## What does this PR do?

This PR has the same changes from #589, that PRs history is not same with the history of our main branch.
Upon trying to rebase this PR, I was getting 54 conflicts due to the folder rename.
The old PR is based on main branch, so I cant force push either, thus this PR

> From Old PR
<img width="425" alt="Screenshot 2024-07-22 at 17 56 40" src="https://github.com/user-attachments/assets/31d9e67f-d74e-42ed-90a9-f30dbdeee984">
<img width="558" alt="Screenshot 2024-07-22 at 17 57 29" src="https://github.com/user-attachments/assets/4c90f884-3bba-46ab-98e4-d9ab5674d58d">


## Type of change

<!-- Please mark the relevant points by using [x] -->

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] Chore (refactoring code, technical debt, workflow improvements)
- [ ] Enhancement (small improvements)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update

## Checklist

<!-- We're starting to get more and more contributions. Please help us making this efficient for all of us and go through this checklist. Please tick off what you did  -->

### Required

- [ ] Read [Contributing Guide](https://github.com/un/inbox/blob/main/CONTRIBUTING.md)
- [ ] Self-reviewed my own code
- [ ] Tested my code in a local environment
- [ ] Commented on my code in hard-to-understand areas
- [ ] Checked for warnings, there are none
- [ ] Removed all `console.logs`
- [ ] Merged the latest changes from main onto my branch with `git pull origin main`
- [ ] My changes don't cause any responsiveness issues

### Appreciated

- [ ] If a UI change was made: Added a screen recording or screenshots to this PR
- [ ] Updated the UnInbox Docs if changes were necessary
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants