Adding Users to Your Wiki Repo
The wiki lives in GitHub. To let a teammate read SOPs and propose changes, the owner adds them as a collaborator on the repo. The teammate then signs in (or signs up) and accepts the invite. Once they have push access, they edit pages directly in the browser and open pull requests for review.
Who does what
Section titled “Who does what”- Owner — sets up the repo, invites teammates, approves merges.
- Team Member — reads SOPs, proposes pull requests when something needs to change.
- Claude — writes, updates, and merges on command.
What the owner does
Section titled “What the owner does”1. Open the repo’s Collaborators page
Section titled “1. Open the repo’s Collaborators page”In your repo on GitHub, go to Settings → Access → Collaborators. The URL pattern is github.com/<your-org>/<your-repo>/settings/access.
2. Click “Add people” and enter their email
Section titled “2. Click “Add people” and enter their email”Use the work email you want them to log in with. GitHub looks for an existing account on that email. If it finds one, the invite goes there. If not, GitHub still sends an invite email and the teammate can finish account setup from the link.
3. Wait for them to accept
Section titled “3. Wait for them to accept”The new entry shows up under Manage access with a “Pending Invite” badge until the teammate accepts. Once they do, they have push access to the repo.
What the teammate does
Section titled “What the teammate does”1. Open the invitation email
Section titled “1. Open the invitation email”GitHub sends an email titled ”noreply@github.com. Click the green Accept invitation button.
2. Sign in or sign up
Section titled “2. Sign in or sign up”If the teammate already has a GitHub account on that email, they sign in. If not, the link drops them into github.com/signup with the email pre-filled. Pick a username, set a password, verify the email with the launch code GitHub sends.
3. Confirm push access
Section titled “3. Confirm push access”After accepting, the repo opens with a green banner: “You now have push access to the
4. Edit a page in the browser
Section titled “4. Edit a page in the browser”Navigate to the file in the repo (under src/content/docs/<section>/), click the pencil icon in the top right of the file view, make the change, scroll to the bottom, and click Propose changes. GitHub creates a new branch named <username>-patch-N and routes you straight to the pull request screen.
5. Open a pull request
Section titled “5. Open a pull request”Fill in a one-line title that names the change and a short description that explains why. Click Create pull request.
Owner reviews and merges
Section titled “Owner reviews and merges”The owner gets a notification, opens the pull request, reviews the diff, leaves comments if needed, and clicks Merge pull request when it is good to go. Cloudflare Pages auto-deploys the change in about 30 seconds.
Definition of done
Section titled “Definition of done”- The teammate’s username appears under Settings → Access → Collaborators without a “Pending Invite” badge.
- The teammate has merged at least one pull request that is now visible on the live wiki.