glab(1)
β¨ glab(1) β the repo members add glow-up β¨
okay bestie, so this is a page from the glab manual (yes, the glab, the GitLab CLI, we stan) and it's all about one specific little command that adds a person to your project. it's giving "invite your friend to the group chat" energy and honestly? iconic. let's get into it π
πΈ NAME πΈ
glab-repo-members-add β literally just: add a member to the project. that's the whole vibe. π«Ά
β SYNOPSIS β
glab repo members add [flags]
no positional args, no drama, just flags. periodt.
π¦ DESCRIPTION π¦
so you wanna add a member to the project with a specified role. that's it, that's the function. but the roles? oh we have a whole lineup, and you're gonna want to know them by heart π
- guest (10) β can view the project. lurker mode, lowkey valid.
- reporter (20) β can view and create issues. they can post, they can't push.
- developer (30) β can push to non-protected branches. main character energy, but not on
mainπ« - maintainer (40) β can manage the project. they run the group chat.
- owner (50) β full access to the project. absolute final boss, no cap. π₯
for custom roles, hit up --role-id with the ID of a custom role defined in the project or group. and listen β if that custom role does not exist, an error is returned. so double-check your ID bestie, don't come crying to me π
β¨ OPTIONS β¨
-e,--expires-at=""β expiration date for the membership, formatted asYYYY-MM-DD. the membership has a scheduled departure, very mysterious of it π-R,--repo=""β select another repository. you can use eitherOWNER/REPOorGROUP/NAMESPACE/REPO. the full URL or Git URL is also accepted. so many ways to say where, we love options π¦-r,--role="developer"β role for the user. valid picks:guest,reporter,developer,maintainer,owner. default isdeveloper, they really said "start them off reasonable" πΈ--role-id=0β ID of a custom role defined in the project or group. for the β¨ bespoke β¨ role enjoyers.-u,--user-id=0β user ID instead of username. numbers only, no names.--username=""β username instead of user-id. names only, no numbers. pick a lane, we support both π
π§ OPTIONS INHERITED FROM PARENT COMMANDS π§
-h,--help[=false]β show help for this command. the classic. the icon. when in doubt,-hit out.
π EXAMPLE π
here's exactly how the cool kids do it, copied with love:
# Add a user as a developer
glab repo members add --username=john.doe --role=developer
# Add a user as a maintainer with expiration date
glab repo members add --username=jane.smith --role=maintainer --expires-at=2024-12-31
# Add a user by ID
glab repo members add --user-id=123 --role=reporter
# Add a user with a custom role
glab repo members add --username=john.doe --role-id=101
see? four whole examples. jane's membership expires at 2024-12-31 and we respect her journey π«Ά
π SEE ALSO π
glab-repo-members(1)β the parent page, go read it next, iykyk π
ngl bestie, if you're passing --role-id, make sure that custom role actually exists in the project or group first. otherwise: error. and not the cute kind. π
and that's the page!! π auto generated by spf13/cobra, dated Nov 2026, and this is glab(1) signing off β slay, stay hydrated, and go add some members πβ¨
π¦ where this page comes from
- arch rolling: glab 1.128.0-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms