Branch was updated using the 'autoupdate branch' Actions workflow.
This commit is contained in:
@@ -12,8 +12,8 @@ redirect_from:
|
||||
topics:
|
||||
- Community
|
||||
---
|
||||
|
||||
To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file.
|
||||
### About contributing guidelines
|
||||
To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
|
||||
|
||||

|
||||
|
||||
@@ -39,10 +39,11 @@ You can create default contribution guidelines for your organization{% if curren
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.files.add-file %}
|
||||
3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive, and can have an extension such as *.md* or *.txt*.
|
||||
3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Rendering differences in prose documents](/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)."
|
||||

|
||||
- To make your contributing guidelines visible in the repository's root directory, type *CONTRIBUTING*.
|
||||
- To make your contributing guidelines visible in the repository's `docs` directory, type *docs/* to create the new directory, then *CONTRIBUTING*.
|
||||
- If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
|
||||
4. In the new file, add contribution guidelines. These could include:
|
||||
- Steps for creating good issues or pull requests.
|
||||
- Links to external documentation, mailing lists, or a code of conduct.
|
||||
|
||||
@@ -23,7 +23,7 @@ Public installation flows have a landing page to enable other people besides the
|
||||
|
||||
### Private installation flow
|
||||
|
||||
Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private, or internal, GitHub Apps can only be installed on the user or organization account of the owner.
|
||||
Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private{% if currentVersion ver_lt "enterprise-server@3.2" or currentVersion == "github-ae@latest" %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner.
|
||||
|
||||
### Changing who can install your GitHub App
|
||||
|
||||
@@ -35,7 +35,7 @@ To change who can install the GitHub App:
|
||||
3. Select the GitHub App whose installation option you want to change.
|
||||

|
||||
{% data reusables.user-settings.github_apps_advanced %}
|
||||
5. Depending on the installation option of your GitHub App, click either **Make public** or **Make internal**.
|
||||
5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**.
|
||||

|
||||
6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App internal**.
|
||||
6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" %}private{% else %}internal{% endif %}**.
|
||||

|
||||
|
||||
@@ -49,6 +49,8 @@ Label | Description
|
||||
|
||||
Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later.
|
||||
|
||||
Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute).
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
|
||||
Organization owners can customize the default labels for repositories in their organization. For more information, see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)."
|
||||
{% endif %}
|
||||
|
||||
Reference in New Issue
Block a user