This repository was archived by the owner on Oct 2, 2023. It is now read-only.
How we are organized on GitHub #2
AaronDewes
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Important: This only works if you're a member of the Citadel GitHub organization. Because we're a community project, you can be added as a member if you did multiple contributions, so it's not impossible.
GitHub teams
We have multiple teams you can tag in a PR / assign a PR to to get a review from them.
Currently, we have
@runcitadel/backend General team of backend developers - Ping these if you're chaning something which requires/allows changes both on the host and the manager/middleware
@runcitadel/design Designers - Ping these if you do UI changes and want to get a Design review
@runcitadel/frontend Frontend devs - Ping these if you do code changes on the frontend and want a code review
@runcitadel/host-system Ping these if you change something in
compose-nonfree@runcitadel/node Ping these if you change something in our JavaScript/TypeScript code if it's not part of the frontend
@runcitadel/docker Ping these if it's regarding docker containers.
Beta Was this translation helpful? Give feedback.
All reactions