Skip to content

Commit

Permalink
learners are already admin through team access, keep repository name …
Browse files Browse the repository at this point in the history
…for searching
  • Loading branch information
colevandersWands committed Dec 21, 2024
1 parent 6989943 commit 10b1f43
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions collaboration/guide/0_repository_setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,22 +6,21 @@ take the time to do this correctly at the beginning.

## Setup and Share a Repository

As a team you will choose the name for your project's repository and select
As a team you will choose the name for your team and select
someone from your team to be the repo owner. This person will fork this
repository and configure it for collaboration:

- Public face of your repository (optional)
- Change your repository's name
- Public face of your repository
- Change your
[repository description](https://stackoverflow.com/questions/7757751/how-do-you-change-a-repository-description-on-github)
- Add or remove topics from your repository
- Update your main README with your group name and an initial overview of your project. (You can change this as much as you want.)
- Under settings in your repository select:
- _Issues_
- _Discussions_
- _Projects_
- _Always suggest updating pull request branches_
- Collaboration Settings
- Add everyone in your team as a contributor with _Admin_ access
- Require a code review for PRs to `main`/`master`
([owanateamachree](https://owanateamachree.medium.com/how-to-protect-the-master-branch-on-github-ab85e9b6b03),
[github docs](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews))
Expand Down

0 comments on commit 10b1f43

Please sign in to comment.