login configuration

[peintnermax]

Definition of Ready

• [ ] I am happy with the code
• [ ] Short description of the feature/issue is added in the pr description
• [ ] PR is linked to the corresponding user story
• [ ] Acceptance criteria are met
• [ ] All open todos and follow ups are defined in a new ticket and justified
• [ ] Deviations from the acceptance criteria and design are agreed with the PO and documented.
• [ ] Vitest unit tests ensure that components produce expected outputs on different inputs.
• [ ] Cypress integration tests ensure that login app pages work as expected on good and bad user inputs, ZITADEL responses or IDP redirects. The ZITADEL API is mocked, IDP redirects are simulated.
• [ ] Playwright acceptances tests ensure that the happy paths of common user journeys work as expected. The ZITADEL API is not mocked but IDP redirects are simulated.
• [ ] No debug or dead code
• [ ] My code has no repetitions

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
typescript-login	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 29, 2025 7:21am

[eliobischof]

👋 Thanks for your contribution @peintnermax!

This repository zitadel/typescript is a read-only mirror of the git subtree at zitadel/zitadel/login. Therefore, we close this pull request automatically.

Your changes are not lost. Submitting them to the main repository is easy:

1. Fork zitadel/zitadel
2. Clone your Zitadel fork git clone https://github.com/<your-owner>/zitadel.git
3. Change directory to your Zitadel forks root.
4. Pull your changes into the Zitadel fork by running make login_pull LOGIN_REMOTE_URL=https://github.com/<your-owner>/typescript.git LOGIN_REMOTE_BRANCH=<your-typescript-fork-branch>.
5. Push your changes and open a pull request to zitadel/zitadel