mirror of
https://github.com/zitadel/zitadel.git
synced 2025-12-06 19:36:41 +00:00
b10455b51f
# Which Problems Are Solved - The previous monorepo in monorepo structure for the login app and its related packages was fragmented, complicated and buggy. - The process for building and testing the login container was inconsistent between local development and CI. - Lack of clear documentation as well as easy and reliable ways for non-frontend developers to reproduce and fix failing PR checks locally. # How the Problems Are Solved - Consolidated the login app and its related npm packages by moving the main package to `apps/login/apps/login` and merging `apps/login/packages/integration` and `apps/login/packages/acceptance` into the main `apps/login` package. - Migrated from Docker Compose-based test setups to dev container-based setups, adding support for multiple dev container configurations: - `.devcontainer/base` - `.devcontainer/turbo-lint-unit` - `.devcontainer/turbo-lint-unit-debug` - `.devcontainer/login-integration` - `.devcontainer/login-integration-debug` - Added npm scripts to run the new dev container setups, enabling exact reproduction of GitHub PR checks locally, and updated the pipeline to use these containers. - Cleaned up Dockerfiles and docker-bake.hcl files to only build the production image for the login app. - Cleaned up compose files to focus on dev environments in dev containers. - Updated `CONTRIBUTING.md` with guidance on running and debugging PR checks locally using the new dev container approach. - Introduced separate Dockerfiles for the login app to distinguish between using published client packages and building clients from local protos. - Ensured the login container is always built in the pipeline for use in integration and acceptance tests. - Updated Makefile and GitHub Actions workflows to use `--frozen-lockfile` for installing pnpm packages, ensuring reproducible installs. - Disabled GitHub release creation by the changeset action. - Refactored the `/build` directory structure for clarity and maintainability. - Added a `clean` command to `docks/package.json`. - Experimentally added `knip` to the `zitadel-client` package for improved linting of dependencies and exports. # Additional Changes - Fixed Makefile commands for consistency and reliability. - Improved the structure and clarity of the `/build` directory to support seamless integration of the login build. - Enhanced documentation and developer experience for running and debugging CI checks locally. # Additional Context - See updated `CONTRIBUTING.md` for new local development and debugging instructions. - These changes are a prerequisite for further improvements to the CI pipeline and local development workflow. - Closes #10276
64 lines
1.8 KiB
YAML
64 lines
1.8 KiB
YAML
name: 🐛 Bug Report
|
|
description: "Create a bug report to help us improve ZITADEL Typescript Library."
|
|
title: "[Bug]: "
|
|
labels: ["bug"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for taking the time to fill out this bug report!
|
|
- type: checkboxes
|
|
id: preflight
|
|
attributes:
|
|
label: Preflight Checklist
|
|
options:
|
|
- label:
|
|
I could not find a solution in the documentation, the existing issues or discussions
|
|
required: true
|
|
- label:
|
|
I have joined the [ZITADEL chat](https://zitadel.com/chat)
|
|
validations:
|
|
required: true
|
|
- type: input
|
|
id: version
|
|
attributes:
|
|
label: Version
|
|
description: Which version of ZITADEL Typescript Library are you using.
|
|
- type: textarea
|
|
id: impact
|
|
attributes:
|
|
label: Describe the problem caused by this bug
|
|
description: A clear and concise description of the problem you have and what the bug is.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: reproduce
|
|
attributes:
|
|
label: To reproduce
|
|
description: Steps to reproduce the behaviour
|
|
placeholder: |
|
|
Steps to reproduce the behavior:
|
|
1. ...
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: screenshots
|
|
attributes:
|
|
label: Screenshots
|
|
description: If applicable, add screenshots to help explain your problem.
|
|
- type: textarea
|
|
id: expected
|
|
attributes:
|
|
label: Expected behavior
|
|
description: A clear and concise description of what you expected to happen.
|
|
- type: textarea
|
|
id: config
|
|
attributes:
|
|
label: Relevant Configuration
|
|
description: Add any relevant configurations that could help us. Make sure to redact any sensitive information.
|
|
- type: textarea
|
|
id: additional
|
|
attributes:
|
|
label: Additional Context
|
|
description: Please add any other infos that could be useful.
|