forgejo-contrib-forgejo-cli-wiki-organizations.md
Watch20
Star402
Fork
You've already forked forgejo-cli
CodeIssues 44Pull requests 8Releases 11Packages 2WikiActivity
Page: Organizations
ActionsAuthenticationBuildingHomeInstallationIssuesOrganizationsPRsRepositoriesUsers
HTTPS
No results
2 Organizations Cyborus edited this page 2026-01-14 11:28:50 -05:00
#Table of Contents
A new organization is created with fj org create <NAME>. The name can only contain alphanumeric characters, _, or -, and can only start and end with alphanumeric characters. If you'd like to set a name that has special characters, you can set a display name with the --full-name option.
Contact and miscellanous information can be included with the --email, --location, and --website options.
The organization can be made private, limited-visibility, or public with the --visibility command. See the Visibility section for more.
To add users to the organization, you must add them to a team within the organization. See the Teams section for more info.
All of the above options can be changed afterwards with fj org edit, except for renaming it. That must be done via the web interface.
You can use fj org view to see info on an organization, fj org list to see a list of all organizations, and with --only-member-of to only list the organizations you are a member of, fj org activity to see everything going on in an organization, and fj org members to see who all is a member of an organization,
An organization's repos can be listed with fj org repo list. A new repository can be created with fj org repo create <ORG> <REPO>, which takes the same arguments as fj repo create, so see its documentation for more info.
An organization can have a set of issue labels that are included in all of its repositories.
A new label can be created with fj org label add. It takes a name, an color (in the form of a hex code), optionally a description, and can be set to be exclusive with other issues of the same scope, if the issue name is of the form {scope}/{name}. These can all be changed afterwards with fj org label edit.
Labels can be listed with fj org label list and removed with fj org label delete.
Organizations have three privacy options: private, limited, or public. Private organizations can only be seen by its members, limited organizations can be viewed by any signed-in user, and public organizations can be viewed by anyone.
In addition to this, your own membership in an organization can be set to private or public. By default your membership is private, so that only other members of the organization can see you are a member. You can view and change your membership privacy with fj org visibility.
Teams are the method of assigning members' permissions to the organization's repositories. By default, the only team is the Owners team who has complete access to the organization. More teams can be created with finer-grain access.
A new team can be added to an organization with fj org team create <ORG> <TEAM>.
Read-only and read-write permissions can be set with --read-permissions and --write-permissions respectively, both taking a comma-separated list of the following permissions:
wikiext_wikiissuesext_issuespullsprojectsactionscodereleasespackagesPermission to create repositories is set with the --can-create-repos flag. Access to the organization's repos is set with fj org team repo add and fj org team repo rm, or access to every repo can be granted with --include-all-repos
A team can be given admin permissions with the --admin flag.
All of the above options can be changed afterwards with fj org team edit.
fj org team member list shows all the members of a team. Users can be added and removed from a team with fj org team member add and fj org team member rm.
You can list all teams with fj org team list, and view a specific team with fj org team view, and its permissions with --list-permissions. All the repos a team has access to can be viewed with fj org team repo list.
Teams can be deleted with fj org team delete