agaric/documentation
10
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add instructions for creating an organization and repo project

Browse source 
on Agaric's Forgejo.
This commit is contained in:
benjamin melançon 2025-01-24 17:04:38 -05:00
parent a62d9f97a0
commit 74127e5e82
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
tools/git-agaric-com-forgejo.md
View file

@ -1,5 +1,22 @@
# git.agaric.com's Forgejo
Create an organization for each client (Forgejo does not support sub-groups).
- https://git.agaric.com/org/create
- **Organization name** should be what you want in the URL— all lowercase, with dashes instead of any spaces (an "Organization full name" can be set in the organization settings later).
- **Visibility** should be either **Public** or **Private** ("Limited" makes no sense for Agaric's diverse clients and initiatives).
- For Drutopia and some other clients, the organization made for them should be public.
- Leave "Repository admin can add and remove access for teams" checked.
After it is created, press the **View example-org** button in the upper right of the screen. From here you can press settings to add a logo, full name, and description.
Then migrate or make a new repository project (**New migration** or **New repository** buttons).
- For migrating:
- Get an API access token from GitLab or GitHub to be able to import issues etc.
- Be sure to uncheck "This repository will be a mirror" generally.
- Be sure to check off what you want to migrate in addition to the code.
- **Visibility** can have "Make repository private" left unchecked to keep it public. In this case it is worth noting why in the **Description**, for example "As a Drutopia project we hope others can learn from and emulate, this project is public."
## User account creation and adding people to a project
As of now, do *not* invite users by e-mail address directly from a Team tab but instead: