Managing repos
Roles, permissions & quota
Everyone in a repo or group has a role. The role decides what they may do.
Role table
| Can⦠| Guest | Reporter | Developer | Maintainer | Owner |
|---|---|---|---|---|---|
| View & create issues | β | β | β | β | β |
| View code, clone | β | β | β | β | |
| Manage labels, assignees, board | β | β | β | β | |
| Push, create branches & merge requests | β | β | β | ||
| Approve merge requests | β | β | β | ||
| Merge into protected branches, manage members, webhooks, mirrors | β | β | |||
| Rename, change visibility, archive, delete the repo | β |
Private or public
- Private β only members know the repo exists. Others see 404 not found.
- Public β anyone can view and clone, even signed out. Only members can push.
Inviting people
Repo: Settings β Members β enter a Jianren account email or nickname β pick a role β Invite.
Group: open the group page β Manage members. Group roles apply to every repo in the group. If someone is also invited directly to a repo, the highest role wins.
Invited people don't need to request Lumbung access β requests are only needed to create your own repos.
Protected branches
Settings β Protected branches sets a branch pattern (e.g. main or release/*), who may push directly, who may merge, and whether force push is allowed. Protected branches can't be deleted.
Quota
Every approved account gets 2 GB for all repos in its personal namespace and the groups it founded. Usage shows on the Lumbung home page. Pushes over quota are rejected β delete old repos or ask an admin for more.