Skip to content

Commit efdd355

Browse files
authored
Merge pull request #32079 from github/repo-sync
repo sync
2 parents dae4613 + 559dd75 commit efdd355

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,11 +30,14 @@ For a submission with a purpose of `Learn`, your repository must have:
3030
- A description.
3131
- A LEARN.md file to provide step-by-step instructions, with text and/or media, on how you built your project. Ideally, your LEARN.md file will deconstruct your project into small components and provide thorough details of each step, so that other students can code their project by following your instructions.
3232
- A README.md file to provide a detailed description of your project.
33+
- A License so others are aware of what they can and cannot do with your source code.
3334

3435
For a submission with a purpose of `Collaborate`, your repository must have:
3536
- A description.
3637
- A README.md file to provide a detailed description of your project.
38+
- A License so others are aware of what they can and cannot do with your source code.
3739
- One or more issues for collaborators to work on.
40+
- CONTRIBUTING.md file to communicate how to contribute to your project.
3841

3942
A good repository submission for both `Learn` and `Collaborate` purposes, is a repository that follows community standards. For more information, see "[About community profiles for public repositories](/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories)."
4043

content/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,9 @@ Some of the features listed below are limited to organizations using {% data var
7373
| Reopen issues they closed themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
7474
| Have an issue assigned to them | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
7575
| Send pull requests from forks of the team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
76-
| Submit reviews on pull requests | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
76+
| [Submit reviews on pull requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
77+
| [Approve or request changes to a pull request with required reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews) | | | **✔️** | **✔️** | **✔️** |
78+
| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **✔️** | **✔️** | **✔️** |
7779
| View published releases | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %}
7880
| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %}
7981
| Edit wikis in public repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
@@ -95,8 +97,6 @@ Some of the features listed below are limited to organizations using {% data var
9597
| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** |
9698
| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** |
9799
| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** |
98-
| Submit reviews that affect a pull request's mergeability | | | **✔️** | **✔️** | **✔️** |
99-
| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **✔️** | **✔️** | **✔️** |
100100
| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %}
101101
| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** |{% endif %}
102102
| Create and edit releases | | | **✔️** | **✔️** | **✔️** |

0 commit comments

Comments
 (0)