зеркало из https://github.com/github/docs.git
docs-bot
GitHub
Коммит
f6a5af84c1
|
|
@ -89,10 +89,8 @@ When you initially configure default setup for {% data variables.product.prodnam
|
|||
{% endif %}
|
||||
|
||||
> [!NOTE]
|
||||
{% ifversion default-setup-pre-enablement %}
|
||||
> If the analyses fail for all {% data variables.product.prodname_codeql %}-supported languages in a repository, default setup will still be enabled, but it will not run any scans or use any {% data variables.product.prodname_actions %} minutes until another {% data variables.product.prodname_codeql %}-supported language is added to the repository or default setup is manually reconfigured, and the analysis of a {% data variables.product.prodname_codeql %}-supported language succeeds.
|
||||
{% else %}
|
||||
> At least one {% data variables.product.prodname_codeql %}-supported language's analysis in a repository must succeed, or else default setup will not be successfully enabled in that repository.
|
||||
{% ifversion default-setup-pre-enablement %}> If the analyses fail for all {% data variables.product.prodname_codeql %}-supported languages in a repository, default setup will still be enabled, but it will not run any scans or use any {% data variables.product.prodname_actions %} minutes until another {% data variables.product.prodname_codeql %}-supported language is added to the repository or default setup is manually reconfigured, and the analysis of a {% data variables.product.prodname_codeql %}-supported language succeeds.
|
||||
{% else %}> At least one {% data variables.product.prodname_codeql %}-supported language's analysis in a repository must succeed, or else default setup will not be successfully enabled in that repository.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ You can also configure workflow automations to keep your {% data variables.proje
|
|||
{% data reusables.projects.classic-project-creation %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-hidden="true" %} **Projects**.
|
||||
1. On the top of your profile page, in the main navigation, click **{% octicon "project" aria-hidden="true" %} Projects**.
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
|
||||
|
|
@ -92,7 +92,7 @@ You can also configure workflow automations to keep your {% data variables.proje
|
|||
{% data reusables.projects.classic-project-creation %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "project" aria-hidden="true" %} **Projects**.{% ifversion projects-v2 %}
|
||||
1. Under your repository name, click **{% octicon "project" aria-hidden="true" %} Projects**.{% ifversion projects-v2 %}
|
||||
1. Click **Projects (classic)**{% endif %}
|
||||
{% data reusables.project-management.click-new-project %}
|
||||
{% data reusables.project-management.create-project-name-description %}
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
|
|||
## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests.
|
||||
1. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-hidden="true" %} **Add cards**.
|
||||
1. In your {% data variables.projects.projects_v1_board %}, click **{% octicon "plus" aria-hidden="true" %} Add cards**.
|
||||
|
||||
1. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers such as `is:issue is:open`. For more information on search qualifiers you can use, see "[AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests)."
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ When you copy a project, the new project will contain the same {% data reusables
|
|||
|
||||
|
||||
|
||||
1. In the menu, click {% octicon "copy" aria-hidden="true" %} **Make a copy**.
|
||||
1. In the menu, click **{% octicon "copy" aria-hidden="true" %} Make a copy**.
|
||||
1. Optionally, if you want all draft issues to be copied with the project, in the "Make a copy" dialog, select **Draft issues will be copied if selected**.{%- ifversion projects-v2-org-templates-improvements %}{%- else %}
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ You can migrate your {% data variables.projects.projects_v1_boards %} to the new
|
|||
|
||||
|
||||
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. On the top of your profile page, in the main navigation, click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
|
@ -48,6 +48,6 @@ You can migrate your {% data variables.projects.projects_v1_boards %} to the new
|
|||
> {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository {% data variables.projects.projects_v1_board %}, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. Under your repository name, click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
1. In the left sidebar, click **Projects (classic)**.
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ The current count of cards and the column's limit is displayed at the top of the
|
|||
|
||||
1. Click {% octicon "kebab-horizontal" aria-label="Column context menu" %} next to the name of the column you want to modify.
|
||||
|
||||
1. In the menu, click {% octicon "number" aria-hidden="true" %} **Set column limit**.
|
||||
1. In the menu, click **{% octicon "number" aria-hidden="true" %} Set column limit**.
|
||||
1. Under "Column limit", type the card limit for this column.
|
||||
1. Optionally, to remove the limit, clear the entry.
|
||||
1. Click **Save**.
|
||||
|
|
@ -41,7 +41,7 @@ The current count of cards and the column's limit is displayed at the top of the
|
|||
In the board layout, you choose any single select or iteration field for your columns. If you drag an item to a new column, the value of that column is applied to the dragged item. For example, if you use the "Status" field for your board columns and then drag an item with a status of `In progress` to the `Done` column, the status of the item will switch to `Done`.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "columns" aria-hidden="true" %} **Column field**.
|
||||
1. Click **{% octicon "columns" aria-hidden="true" %} Column field**.
|
||||
1. Click the field you want to use.
|
||||
|
||||
{% ifversion projects-v2-column-visibility %}
|
||||
|
|
|
|||
|
|
@ -21,11 +21,11 @@ For more information about changing a view to use the roadmap layout, see "[AUTO
|
|||
|
||||
You can set the date or iteration fields that your roadmap will use to position items. When you set a view to a roadmap layout, {% data variables.product.company_short %} will attempt to use existing date and iteration fields you have already set up. For more information on creating new fields, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields)" and "[AUTOTITLE](/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields)."
|
||||
|
||||
1. In the top right of your roadmap, click {% octicon "calendar" aria-hidden="true" %} **Date fields**.
|
||||
1. In the top right of your roadmap, click **{% octicon "calendar" aria-hidden="true" %} Date fields**.
|
||||
|
||||
|
||||
|
||||
1. Optionally, to create a new date or iteration field, click {% octicon "plus" aria-hidden="true" %} **New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
|
||||
1. Optionally, to create a new date or iteration field, click **{% octicon "plus" aria-hidden="true" %} New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
|
||||
1. Select a date or iteration field for "Start date" and "Target date."
|
||||
|
||||
{% ifversion projects-v2-roadmap-markers %}
|
||||
|
|
@ -34,7 +34,7 @@ You can set the date or iteration fields that your roadmap will use to position
|
|||
|
||||
You can configure vertical markers on a roadmap to show your iterations, the dates of items in your project, and the milestones associated with items in your project.
|
||||
|
||||
1. In the top right of your roadmap, click {% octicon "location" aria-hidden="true" %} **Markers**.
|
||||
1. In the top right of your roadmap, click **{% octicon "location" aria-hidden="true" %} Markers**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ You can also hide individual fields using the field headers.
|
|||
|
||||
1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="Status column options" %}.
|
||||
|
||||
1. Click {% octicon "eye-closed" aria-hidden="true" %} **Hide field**.
|
||||
1. Click **{% octicon "eye-closed" aria-hidden="true" %} Hide field**.
|
||||
|
||||
## Grouping by field values
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ You can duplicate an existing view and use it as a base to make further changes.
|
|||
|
||||
1. Switch to the view you want to duplicate.
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "versions" aria-hidden="true" %} **Duplicate view**.
|
||||
1. Click **{% octicon "versions" aria-hidden="true" %} Duplicate view**.
|
||||
|
||||
## Saving changes to a view
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ You can rename your saved views. The name change is automatically saved.
|
|||
|
||||
1. Switch to the view you want to rename.
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "pencil" aria-hidden="true" %} **Rename view**.
|
||||
1. Click **{% octicon "pencil" aria-hidden="true" %} Rename view**.
|
||||
1. Type the new name for your view.
|
||||
1. To save your changes, press <kbd>Return</kbd>.
|
||||
|
||||
|
|
@ -60,4 +60,4 @@ You can rename your saved views. The name change is automatically saved.
|
|||
|
||||
1. Switch to the view you want to delete.
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "trash" aria-hidden="true" %} **Delete view**.
|
||||
1. Click **{% octicon "trash" aria-hidden="true" %} Delete view**.
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ topics:
|
|||
You can browse all of your projects, regardless of where they are located. You can see the projects you have recently viewed and the projects you have created, and apply your own filters.
|
||||
|
||||
1. In the top left of any page, click {% octicon "three-bars" aria-label="Open global navigation menu" %} to open the global navigation menu.
|
||||
1. In the menu, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. In the menu, click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
{% data reusables.projects.index-select %}
|
||||
|
||||
## Finding an organization's projects
|
||||
|
|
@ -23,7 +23,7 @@ You can view and filter all the projects owned by an organization that you have
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
1. Under the organization name, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. Under the organization name, click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
{% data reusables.projects.index-select %}
|
||||
|
||||
## Finding projects owned by your personal account
|
||||
|
|
@ -31,7 +31,7 @@ You can view and filter all the projects owned by an organization that you have
|
|||
You can view and filter projects that you have created under your personal account.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On your profile, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. On your profile, click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
{% data reusables.projects.index-select %}
|
||||
|
||||
## Finding projects linked to a repository
|
||||
|
|
@ -39,7 +39,7 @@ You can view and filter projects that you have created under your personal accou
|
|||
Repositories can be linked to organization-level and user-level projects. You can browse and filter the projects that are linked to a specific repository. For more information on linking projects to a repository, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository)."
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
|
||||
1. Click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. Click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ You can also link a project to specific teams in an organization and then browse
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
1. Click {% octicon "project" aria-hidden="true" %} **Projects**.
|
||||
1. Click **{% octicon "project" aria-hidden="true" %} Projects**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ Specify a priority for all issues in your project.
|
|||
Next, group all of the items in your project by priority to make it easier to focus on the high priority items.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "rows" aria-hidden="true" %} **Group**.
|
||||
1. Click **{% octicon "rows" aria-hidden="true" %} Group**.
|
||||
1. Click **Priority**.
|
||||
|
||||
Now, move issues between groups to change their priority.
|
||||
|
|
@ -121,7 +121,7 @@ When you changed the layout, your project displayed an indicator to show that th
|
|||
To indicate the purpose of the view, give it a descriptive name.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "pencil" aria-hidden="true" %} **Rename view**.
|
||||
1. Click **{% octicon "pencil" aria-hidden="true" %} Rename view**.
|
||||
1. Type the new name for your view.
|
||||
1. To save changes, press <kbd>Return</kbd>.
|
||||
|
||||
|
|
@ -143,7 +143,7 @@ Finally, add a built in workflow to set the status to **Todo** when an item is a
|
|||
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
|
||||
|
||||
1. In the menu, click {% octicon "workflow" aria-hidden="true" %} **Workflows**.
|
||||
1. In the menu, click **{% octicon "workflow" aria-hidden="true" %} Workflows**.
|
||||
1. Under **Default workflows**, click **Item added to project**.
|
||||
1. Next to **When**, ensure that both `issues` and `pull requests` are selected.
|
||||
1. Next to **Set**, select **Status:Todo**.
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ You can archive an item to keep the context about the item in the project but re
|
|||
|
||||
|
||||
|
||||
1. In the menu, click {% octicon "archive" aria-hidden="true" %} **Archived items**.
|
||||
1. In the menu, click **{% octicon "archive" aria-hidden="true" %} Archived items**.
|
||||
1. Optionally, to filter the archived items displayed, type your filter into the text box above the list of items. For more information about the available filters, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
|
||||
1. To the left of each item title, select the items you would like to restore.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ You can list relevant projects in a repository. You can only list projects that
|
|||
In order for repository members to see a project listed in a repository, they must have visibility for the project. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)."
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
|
||||
1. Click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. Click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
|
||||
1. Click **Link a project**.
|
||||
1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository.
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ Teams are granted read permissions on any project they are added to. This permis
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
1. Click {% octicon "project" aria-hidden="true" %} **Projects**.
|
||||
1. Click **{% octicon "project" aria-hidden="true" %} Projects**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ allowTitleToDifferFromFilename: true
|
|||
You can download a view as a _.tsv_ (tab-separated) file.
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your repository.
|
||||
1. Click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. Click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
|
|
|
|||
|
|
@ -71,7 +71,7 @@ You can filter the list of projects in your organization to only show projects s
|
|||
If you have write or admin permissions for a project in your organization, you can choose to copy the project as a template. This will make a duplicate of the current project—copying the {% data reusables.projects.what-gets-copied %} —and set that copied project as a template for your organization.
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. In the "Templates" section, click {% octicon "duplicate" aria-hidden="true" %} **Copy as template**.
|
||||
1. In the "Templates" section, click **{% octicon "duplicate" aria-hidden="true" %} Copy as template**.
|
||||
|
||||
{% ifversion projects-v2-org-templates-GA-updates %}
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ If your project makes use of iteration fields, you can use the roadmap layout to
|
|||
1. Click the name of the iteration field you want to adjust.
|
||||
1. To add a new iteration of the same duration, click **Add iteration**.
|
||||
|
||||
1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-hidden="true" %} **More options**, select a starting date and duration, and click **Add**.
|
||||
1. Optionally, to customize the duration of the new iteration and when it will start, click **{% octicon "triangle-down" aria-hidden="true" %} More options**, select a starting date and duration, and click **Add**.
|
||||
|
||||
1. Click **Save changes**.
|
||||
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ You can open a new issue from a specific line or lines of code in a file or pull
|
|||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Locate the code you want to reference in an issue:
|
||||
* To open an issue about code in a file, navigate to the file.
|
||||
* To open an issue about code in a pull request, navigate to the pull request and click {% octicon "diff" aria-hidden="true" %} **Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
|
||||
* To open an issue about code in a pull request, navigate to the pull request and click **{% octicon "diff" aria-hidden="true" %} Files changed**. Then, browse to the file that contains the code you want included in your comment, and click **View**.
|
||||
{% data reusables.repositories.choose-line-or-range %}
|
||||
1. To the left of the code range, click {% octicon "kebab-horizontal" aria-label="Code line X options" %}. In the dropdown menu, click **Reference in new issue**.
|
||||
|
||||
|
|
@ -107,7 +107,7 @@ When you create an issue from a discussion, the contents of the discussion post
|
|||
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "issue-opened" aria-hidden="true" %} **Create issue from discussion**.
|
||||
1. In the right sidebar, click **{% octicon "issue-opened" aria-hidden="true" %} Create issue from discussion**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ You can also make changes to the issue description. The edit history is availabl
|
|||
|
||||
|
||||
|
||||
1. In the menu, click {% octicon "pencil" aria-hidden="true" %} **Edit**.
|
||||
1. In the menu, click **{% octicon "pencil" aria-hidden="true" %} Edit**.
|
||||
1. Type your changes to the issue description.
|
||||
1. Click **Save**.
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ With dependency insights you can view vulnerabilities, licenses, and other impor
|
|||
|
||||
|
||||
1. To filter by a vulnerability status, a license, or a combination of the two, click the results in the **Open security advisories** and **Licenses** graphs.
|
||||
1. To see which dependents in your organization are using each library, next to a vulnerability, click {% octicon "package" aria-hidden-"true" %} **X dependents**.
|
||||
1. To see which dependents in your organization are using each library, next to a vulnerability, click **{% octicon "package" aria-hidden-"true" %} X dependents**.
|
||||
|
||||
## Further reading
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ You can access {% data variables.product.company_short %}'s compliance reports i
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.compliance %}
|
||||
1. To the right of the report you want to access, click {% octicon "download" aria-hidden="true" %} **Download** or {% octicon "link-external" aria-hidden="true" %} **View**.
|
||||
1. To the right of the report you want to access, click **{% octicon "download" aria-hidden="true" %} Download** or **{% octicon "link-external" aria-hidden="true" %} View**.
|
||||
|
||||
{% data reusables.security.compliance-report-screenshot %}
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ If a team's access to a {% data variables.projects.projects_v1_board %} is inher
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
1. Above the team's conversation, click {% octicon "project" aria-hidden="true" %} **Projects**.
|
||||
1. Above the team's conversation, click **{% octicon "project" aria-hidden="true" %} Projects**.
|
||||
|
||||
|
||||
1. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the permission level dropdown menu.
|
||||
|
|
|
|||
|
|
@ -199,7 +199,7 @@ For each repository in your organization, you can see how much cache storage a r
|
|||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, click {% octicon "play" aria-hidden="true" %} **Actions**, then click **Caches**.
|
||||
1. In the left sidebar, click **{% octicon "play" aria-hidden="true" %} Actions**, then click **Caches**.
|
||||
1. Review the list of repositories for information about their {% data variables.product.prodname_actions %} caches. You can click on a repository name to see more detail about the repository's caches.
|
||||
|
||||
{% ifversion actions-cache-admin-ui %}
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ You{% ifversion custom-org-roles %}, and any users with the "Edit custom propert
|
|||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.access-custom-properties %}
|
||||
1. Click the "Set values" tab.
|
||||
1. Select one or more repositories from the list and click {% octicon "pencil" aria-hidden="true" %} **Edit properties**.
|
||||
1. Select one or more repositories from the list and click **{% octicon "pencil" aria-hidden="true" %} Edit properties**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -72,5 +72,5 @@ You can search for repositories in your organization by custom properties values
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
1. Under your organization name, click {% octicon "repo" aria-hidden="true" %} **Repositories**.
|
||||
1. Under your organization name, click **{% octicon "repo" aria-hidden="true" %} Repositories**.
|
||||
1. In the search bar, type `prop` to see a list of all custom properties in your organization, and select the property you'd like to search by.
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ If you're an organization owner or you have team maintainer permissions in both
|
|||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.teams %}
|
||||
1. In the list of teams, click the name of the team where you'd like to add the child team.
|
||||
1. At the top of the team page, click {% octicon "people" aria-hidden="true" %} **Teams**.
|
||||
1. At the top of the team page, click **{% octicon "people" aria-hidden="true" %} Teams**.
|
||||
|
||||
{% ifversion global-nav-update %}
|
||||
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ You can find and view a package located in the repositories of an organization y
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
1. Under your organization name, click {% octicon "package" aria-hidden="true" %} **Packages**.
|
||||
1. Under your organization name, click **{% octicon "package" aria-hidden="true" %} Packages**.
|
||||
{% data reusables.package_registry.navigate-to-packages %}
|
||||
|
||||
## Viewing your packages
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ You can set commit permissions when you first create a pull request from a fork.
|
|||
## Enabling repository maintainer permissions on existing pull requests
|
||||
|
||||
1. On {% data variables.product.product_name %}, navigate to the main page of the upstream repository of your pull request.
|
||||
1. Under the upstream repository name, click {% octicon "git-pull-request" aria-hidden="true" %} **Pull requests**.
|
||||
1. Under the upstream repository name, click **{% octicon "git-pull-request" aria-hidden="true" %} Pull requests**.
|
||||
{% ifversion global-nav-update %}
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Organizational rulesets that apply to branches of a repository will no longer al
|
|||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.navigate-to-branches %}
|
||||
1. Next to the branch you want to rename, select the {% octicon "kebab-horizontal" aria-label="More" %} dropdown menu, then click {% octicon "pencil" aria-label="Rename branch" %} **Rename branch**.
|
||||
1. Next to the branch you want to rename, select the {% octicon "kebab-horizontal" aria-label="More" %} dropdown menu, then click **{% octicon "pencil" aria-label="Rename branch" %} Rename branch**.
|
||||
1. Type a new name for the branch.
|
||||
1. Review the information about local environments, then click **Rename branch**.
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ An empty repository contains no files. It's often made if you don't initialize t
|
|||
|
||||
|
||||
|
||||
Alternatively, to clone your repository in Desktop, click {% octicon "desktop-download" aria-hidden="true" %} **Set up in Desktop** and follow the prompts to complete the clone.
|
||||
Alternatively, to clone your repository in Desktop, click **{% octicon "desktop-download" aria-hidden="true" %} Set up in Desktop** and follow the prompts to complete the clone.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ allowTitleToDifferFromFilename: true
|
|||
|
||||
## Disabling {% data variables.projects.projects_v2 %} in a repository
|
||||
|
||||
When you disable {% data variables.projects.projects_v2 %} in a repository, linked projects will no longer be available in the repository's {% octicon "table" aria-hidden="true" %} **Projects** tab. Linked projects will remain accessible at an organization or user level.
|
||||
When you disable {% data variables.projects.projects_v2 %} in a repository, linked projects will no longer be available in the repository's **{% octicon "table" aria-hidden="true" %} Projects** tab. Linked projects will remain accessible at an organization or user level.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@ By default, when you create a new repository in your personal account, workflows
|
|||
You can use the steps below to configure whether {% ifversion internal-actions %}actions and {% endif %}reusable workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see "[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." Alternatively, you can use the REST API to set, or get details of the level of access. For more information, see "[AUTOTITLE](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository)" and "[AUTOTITLE](/rest/actions/permissions#set-the-level-of-access-for-workflows-outside-of-the-repository)."{% endif %}
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under **Access**, choose one of the access settings:
|
||||
|
||||
|
|
@ -150,7 +150,7 @@ You can use the steps below to configure whether actions and reusable workflows
|
|||
### Managing access for a private repository
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under **Access**, choose one of the access settings:
|
||||
|
||||
|
|
@ -165,7 +165,7 @@ You can use the steps below to configure whether actions and reusable workflows
|
|||
### Managing access for a private repository in an organization
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under **Access**, choose one of the access settings:
|
||||
|
||||
|
|
@ -178,7 +178,7 @@ You can use the steps below to configure whether actions and reusable workflows
|
|||
{% ifversion fpt %}{% else %}
|
||||
|
||||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the private repository.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. Under your repository name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
|
||||
{% data reusables.repositories.settings-sidebar-actions-general %}
|
||||
1. Under **Access**, choose one of the access settings:
|
||||
* **Not accessible** - Workflows in other repositories cannot access this repository.
|
||||
|
|
|
|||
|
|
@ -28,14 +28,14 @@ You can download the source code archives in three ways.
|
|||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
1. Scroll down to the "Assets" section of the release.
|
||||
1. To download the source code, click {% octicon "file-zip" aria-hidden="true" %} **Source code (zip)** or {% octicon "file-zip" aria-hidden="true" %} **Source code (tar.gz)**.
|
||||
1. To download the source code, click **{% octicon "file-zip" aria-hidden="true" %} Source code (zip)** or **{% octicon "file-zip" aria-hidden="true" %} Source code (tar.gz)**.
|
||||
|
||||
### Downloading source code archives from a tag
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
1. At the top of the Releases page, click **Tags**.
|
||||
1. To download the source code, click {% octicon "file-zip" aria-label="The ZIP icon" %} **zip** or {% octicon "file-zip" aria-label="The ZIP icon" %} **tar.gz**.
|
||||
1. To download the source code, click **{% octicon "file-zip" aria-label="The ZIP icon" %} zip** or **{% octicon "file-zip" aria-label="The ZIP icon" %} tar.gz**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -79,8 +79,8 @@ Symbol search is a feature of code search. For more information, see "[AUTOTITLE
|
|||
* To search for a symbol in the repository as a whole, in the symbols pane, click **Search for this symbol in this repository**. To search for a symbol in all repositories on {% data variables.product.prodname_dotcom %}, click **all repositories**.
|
||||
|
||||
1. To navigate between references to a symbol, click {% octicon "chevron-down" aria-label="The downwards-facing chevron icon" %} or {% octicon "chevron-up" aria-label="The upwards-facing chevron icon" %}.
|
||||
1. To navigate to a specific reference to a symbol, click a result of the symbol search under {% octicon "chevron-down" aria-label="The downwards-facing chevron icon" %} **In this file**.
|
||||
1. To exit the search for a specific symbol, click {% octicon "arrow-left" aria-label="The left arrow icon" %} **All Symbols**.
|
||||
1. To navigate to a specific reference to a symbol, click a result of the symbol search under **{% octicon "chevron-down" aria-label="The downwards-facing chevron icon" %} In this file**.
|
||||
1. To exit the search for a specific symbol, click **{% octicon "arrow-left" aria-label="The left arrow icon" %} All Symbols**.
|
||||
{% endif %}
|
||||
|
||||
## Jumping to the definition of a function or method
|
||||
|
|
|
|||
|
|
@ -40,11 +40,11 @@ For more information about the search syntax of code search, see "[AUTOTITLE](/s
|
|||
## Creating and managing saved searches
|
||||
|
||||
1. In the top navigation of {% data variables.product.prodname_dotcom %}, click the search bar and type `saved:`.
|
||||
1. Under the search bar, in the "Saved queries" section, click {% octicon "plus-circle" aria-hidden="true" %} **Manage saved searches**.
|
||||
1. Under the search bar, in the "Saved queries" section, click **{% octicon "plus-circle" aria-hidden="true" %} Manage saved searches**.
|
||||
1. In the pop-up window, type both the name you want for your saved search and the query you want to save.
|
||||
1. To finish creating your saved search, click **Create saved search**.
|
||||
1. To see your saved search, click the search bar. Your saved search will be in the "Saved queries" section. Clicking on a saved search entry will add the query to the search bar and filter the suggestions accordingly.
|
||||
1. To manage a saved search, type `saved:` in the search bar, then click {% octicon "plus-circle" aria-hidden="true" %} **Manage saved searches**.
|
||||
1. To manage a saved search, type `saved:` in the search bar, then click **{% octicon "plus-circle" aria-hidden="true" %} Manage saved searches**.
|
||||
* To edit a saved search, to the right of the search, click {% octicon "pencil" aria-label="The pencil icon" %}.
|
||||
* To delete a saved search, to the right of the search, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ Once you start typing a search query, you will see a list of completions and sug
|
|||
{% else %}
|
||||
|
||||
1. On {% data variables.product.prodname_mobile %}, navigate to the main page of a repository.
|
||||
1. Tap {% octicon "file-code" aria-hidden="true" %} **Code**, then tap the search bar.
|
||||
1. Tap **{% octicon "file-code" aria-hidden="true" %} Code**, then tap the search bar.
|
||||
{% data reusables.search.type-code-search-query-step %}
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -60,5 +60,5 @@ You can export your sponsorship transactions by month. {% data variables.product
|
|||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.your-sponsors-tab %}
|
||||
1. In the top-right, click {% octicon "download" aria-hidden="true" %} **Export**.
|
||||
1. In the top-right, click **{% octicon "download" aria-hidden="true" %} Export**.
|
||||
1. Choose a time frame and a format for the data you'd like to export, then click **Start export**.
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ You can access the sponsorships dashboard through your organization's profile.
|
|||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
1. Under your organization name, click {% octicon "heart" aria-hidden="true" %} **Sponsoring**.
|
||||
1. Under your organization name, click **{% octicon "heart" aria-hidden="true" %} Sponsoring**.
|
||||
|
||||
## Sponsorship fees
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ shortTitle: Attribute sponsorships
|
|||
|
||||
1. Navigate to the organization whose sponsorships you want to attribute to another organization.
|
||||
{% data reusables.organizations.navigate-to-sponsoring %}
|
||||
1. In the sidebar, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. In the sidebar, click **{% octicon "gear" aria-hidden="true" %} Settings**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ You can view your {% data variables.product.company_short %} Invoiced Sponsor Ag
|
|||
|
||||
1. Navigate to the organization.
|
||||
{% data reusables.organizations.navigate-to-sponsoring %}
|
||||
1. In the sidebar, click {% octicon "graph" aria-label="The graph icon" %} **Insights**.
|
||||
1. In the sidebar, click **{% octicon "graph" aria-label="The graph icon" %} Insights**.
|
||||
1. Under your balance, click **{% data variables.product.company_short %} Invoiced Sponsor Agreement** to view the agreement.
|
||||
|
||||
## Understanding your {% data variables.product.prodname_sponsors %} invoice
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
1. Under "Profile Picture", select {% octicon "pencil" aria-hidden="true" %} **Edit**, then click **Upload a photo...**.
|
||||
1. Under "Profile Picture", select **{% octicon "pencil" aria-hidden="true" %} Edit**, then click **Upload a photo...**.
|
||||
|
||||
|
||||
1. Select an image, then click **Upload**.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
{% ifversion fpt %}
|
||||
1. Navigate to the main page of the organization or repository.
|
||||
1. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
|
||||
1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
|
||||
1. In the left sidebar, click **Actions**, then click **Runners**.
|
||||
{% elsif ghec %}
|
||||
1. Navigate to your runner settings:
|
||||
* **In an organization or repository**: Navigate to the main page, then click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
|
||||
* **In an organization or repository**: Navigate to the main page, then click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
|
||||
* **If using an enterprise account**: Navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.github %}, then clicking **Your enterprises**, then clicking the enterprise.
|
||||
1. Navigate to the {% data variables.product.prodname_actions %} settings:
|
||||
* **In an organization or repository**: Click **Actions** in the left sidebar, then click **Runners**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Navigate to the main page of the organization where your runner groups are located.
|
||||
1. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
|
||||
1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
|
||||
{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In your organization or repository, navigate to the main page and click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
|
||||
1. In your organization or repository, navigate to the main page and click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Navigate to the main page of the organization where your self-hosted runner group is registered.
|
||||
1. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
|
||||
1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
|
||||
{% data reusables.organizations.settings-sidebar-actions-runners %}
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Navigate to the main page of the repository where your self-hosted runner group is registered.
|
||||
1. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
|
||||
1. Click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
|
||||
{% data reusables.organizations.settings-sidebar-actions-runners %}
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%}
|
||||
1. In the left sidebar, click {% octicon "play" aria-hidden="true" %} **Actions**, then click **General**.
|
||||
1. In the left sidebar, click **{% octicon "play" aria-hidden="true" %} Actions**, then click **General**.
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
|
||||
1. In the left sidebar, click {% octicon "play" aria-hidden="true" %} **Actions**, then click **Runner groups**.
|
||||
1. In the left sidebar, click **{% octicon "play" aria-hidden="true" %} Actions**, then click **Runner groups**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the left sidebar, click {% octicon "play" aria-hidden="true" %} **Actions**, then click **Runners**.
|
||||
1. In the left sidebar, click **{% octicon "play" aria-hidden="true" %} Actions**, then click **Runners**.
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ Maintainers with write access to a repository can use the following procedure to
|
|||
{% data reusables.repositories.choose-pr-review %}
|
||||
{% data reusables.repositories.changed-files %}
|
||||
1. Inspect the proposed changes in the pull request and ensure that you are comfortable running your workflows on the pull request branch. You should be especially alert to any proposed changes in the `.github/workflows/` directory that affect workflow files.
|
||||
1. If you are comfortable with running workflows on the pull request branch, return to the {% octicon "comment-discussion" aria-hidden="true" %} **Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
|
||||
1. If you are comfortable with running workflows on the pull request branch, return to the **{% octicon "comment-discussion" aria-hidden="true" %} Conversation** tab, and under "Workflow(s) awaiting approval", click **Approve and run**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the "Archive" section of the sidebar, click {% octicon "log" aria-hidden="true" %} **Logs**, then click **Audit log**.
|
||||
1. In the "Archive" section of the sidebar, click **{% octicon "log" aria-hidden="true" %} Logs**, then click **Audit log**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. On the left side of the page, in the enterprise account sidebar, click {% octicon "credit-card" aria-hidden="true" %} **Billing & Licensing**.
|
||||
1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. On the left side of the page, in the organization sidebar, click {% octicon "credit-card" aria-hidden="true" %} **Billing & Licensing**.
|
||||
1. On the left side of the page, in the organization sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
1. Sign into {% data variables.product.prodname_classroom_with_url %}.
|
||||
1. Navigate to a classroom.
|
||||
1. In the {% octicon "repo" aria-hidden="true" %} **Assignments** tab, create the assignment.
|
||||
1. In the **{% octicon "repo" aria-hidden="true" %} Assignments** tab, create the assignment.
|
||||
* If this your first assignment, click **Create an assignment**.
|
||||
* Otherwise, click **New assignment** on the right side.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Optionally, to remove all filters, searches, and sorts, click {% octicon "x" aria-hidden="true" %} **Clear current search query, filters, and sorts**.
|
||||
1. Optionally, to remove all filters, searches, and sorts, click **{% octicon "x" aria-hidden="true" %} Clear current search query, filters, and sorts**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under the classroom name, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. Under the classroom name, click **{% octicon "gear" aria-hidden="true" %} Settings**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under the classroom name, click {% octicon "people" aria-hidden="true" %} **Students**.
|
||||
1. Under the classroom name, click **{% octicon "people" aria-hidden="true" %} Students**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
You can see every available codespace that you have created on the "Your codespaces" page. To display this page, in the top-left corner of {% data variables.product.github %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click {% octicon "codespaces" aria-hidden="true" %} **Codespaces**. This takes you to [github.com/codespaces](https://github.com/codespaces).
|
||||
You can see every available codespace that you have created on the "Your codespaces" page. To display this page, in the top-left corner of {% data variables.product.github %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "codespaces" aria-hidden="true" %} Codespaces**. This takes you to [github.com/codespaces](https://github.com/codespaces).
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the top-left corner of {% data variables.product.github %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click {% octicon "codespaces" aria-hidden="true" %} **Codespaces** to take you to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces).
|
||||
1. In the top-left corner of {% data variables.product.github %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "codespaces" aria-hidden="true" %} Codespaces** to take you to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces).
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
When you have created a team in the enterprise, you can assign licenses to all members of the team.
|
||||
|
||||
{% data reusables.billing.enterprise-billing-menu %}
|
||||
1. Under {% octicon "credit-card" aria-hidden="true" %} **Billing & Licensing**, click **Licensing**.
|
||||
1. Under **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**, click **Licensing**.
|
||||
1. In the "{% data variables.product.prodname_copilot_business_short %}" section, click **Manage seats**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. At the top of the app, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch** and then in the list of branches, click the branch that you want to base your new branch on.
|
||||
1. At the top of the app, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch** and then in the list of branches, click the branch that you want to base your new branch on.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. In {% data variables.product.prodname_desktop %}, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**.
|
||||
1. In {% data variables.product.prodname_desktop %}, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. If you are not already on the branch where the changes are stashed, in the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch with stashed changes.
|
||||
1. If you are not already on the branch where the changes are stashed, in the repository bar, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch**, then click the branch with stashed changes.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to delete.
|
||||
1. In the repository bar, click **{% octicon "git-branch" aria-hidden="true" %} Current Branch**, then click the branch that you want to delete.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
1. Under your repository or organization name, click {% octicon "comment-discussion" aria-hidden="true" %} **Discussions**.
|
||||
1. Under your repository or organization name, click **{% octicon "comment-discussion" aria-hidden="true" %} Discussions**.
|
||||
|
||||
{% ifversion global-nav-update %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Under {% octicon "gear" aria-hidden="true" %} **Settings**, click **Billing**.
|
||||
1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Billing**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. To review a list of IdP groups, in the left sidebar, click {% octicon "key" aria-hidden="true" %} **Identity provider**.
|
||||
1. To review a list of IdP groups, in the left sidebar, click **{% octicon "key" aria-hidden="true" %} Identity provider**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. On the left side of the page, in the enterprise account sidebar, click {% octicon "checklist" aria-hidden="true" %} **Compliance**.
|
||||
1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "checklist" aria-hidden="true" %} Compliance**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the enterprise account sidebar, click {% octicon "plug" aria-hidden="true" %} **{% data variables.product.prodname_github_connect %}**.
|
||||
1. In the enterprise account sidebar, click **{% octicon "plug" aria-hidden="true" %} {% data variables.product.prodname_github_connect %}**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under {% octicon "gear" aria-hidden="true" %} **Settings**, click **{% ifversion ghec %}Licensing{% elsif ghes %}License{% endif %}**. {% ifversion enhanced-billing-platform %}
|
||||
1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **{% ifversion ghec %}Licensing{% elsif ghes %}License{% endif %}**. {% ifversion enhanced-billing-platform %}
|
||||
|
||||
>[!NOTE] If you are on the enhanced billing platform, the licensing page has been relocated. See "[AUTOTITLE](/billing/using-the-enhanced-billing-platform-for-enterprises/gathering-insights-on-your-spending#viewing-license-usage)."{% endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Under {% ifversion ghes %} {% octicon "law" aria-hidden="true" %} **Policies**{% else %}"{% octicon "gear" aria-hidden="true" %} Settings"{% endif %}, click **Options**.
|
||||
1. Under {% ifversion ghes %} **{% octicon "law" aria-hidden="true" %} Policies**{% else %}"{% octicon "gear" aria-hidden="true" %} Settings"{% endif %}, click **Options**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. On the left side of the page, in the enterprise account sidebar, click {% octicon "person" aria-hidden="true" %} **People**.
|
||||
1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "person" aria-hidden="true" %} People**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. On the left side of the page, in the enterprise account sidebar, click {% octicon "law" aria-hidden="true" %} **Policies**.
|
||||
1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "law" aria-hidden="true" %} Policies**.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{%- ifversion ghec or ghes %}
|
||||
1. Under {% octicon "gear" aria-hidden="true" %} **Settings**, click **Authentication security**.
|
||||
1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Authentication security**.
|
||||
{%- else %}
|
||||
1. Under {% octicon "gear" aria-hidden="true" %} **Settings**, click **Security**.
|
||||
1. Under **{% octicon "gear" aria-hidden="true" %} Settings**, click **Security**.
|
||||
{%- endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. On the left side of the page, in the enterprise account sidebar, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "gear" aria-hidden="true" %} Settings**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
Optionally, to view the current configuration for all organizations in the enterprise account before you change the setting, click {% octicon "eye" aria-hidden="true" %} **View your organizations' current configurations**.
|
||||
Optionally, to view the current configuration for all organizations in the enterprise account before you change the setting, click **{% octicon "eye" aria-hidden="true" %} View your organizations' current configurations**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
1. In the upper-right corner of the page, click {% octicon "gear" aria-hidden="true" %} **Admin**.
|
||||
1. In the upper-right corner of the page, click **{% octicon "gear" aria-hidden="true" %} Admin**.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,2 +1,2 @@
|
|||
1. In the upper-right corner of the page, click {% octicon "shield" aria-hidden="true" %} **Security**.
|
||||
1. In the upper-right corner of the page, click **{% octicon "shield" aria-hidden="true" %} Security**.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{% ifversion code-view-ui %}
|
||||
1. Above the list of files, select the **Add file** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %} dropdown menu, then click {% octicon "plus" aria-label="The plus sign icon" %} **Create new file**.
|
||||
1. Above the list of files, select the **Add file** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %} dropdown menu, then click **{% octicon "plus" aria-label="The plus sign icon" %} Create new file**.
|
||||
|
||||
Alternatively, you can click {% octicon "plus" aria-label="The plus sign icon" %} in the file tree view on the left.
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Click {% octicon "plus" aria-hidden="true" %} **Add**.
|
||||
1. Click **{% octicon "plus" aria-hidden="true" %} Add**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. To open {% data variables.product.prodname_marketplace %}, in the top-left corner of {% data variables.product.prodname_dotcom %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click {% octicon "gift" aria-hidden="true" %} **Marketplace**.
|
||||
1. To open {% data variables.product.prodname_marketplace %}, in the top-left corner of {% data variables.product.prodname_dotcom %}, select {% octicon "three-bars" aria-label="Open global navigation menu" %}, then click **{% octicon "gift" aria-hidden="true" %} Marketplace**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under your organization name, click {% octicon "graph" aria-hidden="true" %} **Insights**.
|
||||
1. Under your organization name, click **{% octicon "graph" aria-hidden="true" %} Insights**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under your organization name, click {% octicon "heart" aria-hidden="true" %} **Sponsoring**.
|
||||
1. Under your organization name, click **{% octicon "heart" aria-hidden="true" %} Sponsoring**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
1. Under your organization name, click {% octicon "gear" aria-hidden="true" %} **Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-label="More" %}** dropdown menu, then click **Settings**.
|
||||
1. Under your organization name, click **{% octicon "gear" aria-hidden="true" %} Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-label="More" %}** dropdown menu, then click **Settings**.
|
||||
|
||||
{% ifversion global-nav-update %}
|
||||
|
||||
|
|
|
|||
|
|
@ -10,11 +10,11 @@ If a repository is targeted by a ruleset created at the organization level, only
|
|||
|
||||
#### Targeting all repositories in your organization
|
||||
|
||||
To target all repositories in your organization, in the "Target repositories" section, select {% octicon "goal" aria-hidden="true" %} **Target: REPOSITORIES**, then click **All repositories**.
|
||||
To target all repositories in your organization, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" %} Target: REPOSITORIES**, then click **All repositories**.
|
||||
|
||||
#### Targeting repositories by naming convention in your organization
|
||||
|
||||
1. To target a dynamic list of repositories in your organization by naming convention, in the "Target repositories" section, select {% octicon "goal" aria-hidden="true" %} **Target: REPOSITORIES**, then click **Dynamic list of repositories**.
|
||||
1. To target a dynamic list of repositories in your organization by naming convention, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" %} Target: REPOSITORIES**, then click **Dynamic list of repositories**.
|
||||
1. To begin defining a targeting pattern, in the "Targeting criteria" section, select **Add a target** {% octicon "triangle-down" aria-hidden="true" %}, then click **Include by pattern** or **Exclude by pattern**.
|
||||
1. In the modal dialog that appears, enter a repository naming pattern using `fnmatch` syntax, then click **Add Inclusion pattern** or **Add Exclusion pattern**. For more information on `fnmatch` syntax, see "[Using `fnmatch` syntax](#using-fnmatch-syntax)."
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ To target all repositories in your organization, in the "Target repositories" se
|
|||
|
||||
You can target repositories in your organization by custom properties. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)."
|
||||
|
||||
1. To target a dynamic list of repositories in your organization by properties, in the "Target repositories" section, select {% octicon "goal" aria-hidden="true" %} **Target: REPOSITORIES**, then click **Dynamic list by property**.
|
||||
1. To target a dynamic list of repositories in your organization by properties, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" %} Target: REPOSITORIES**, then click **Dynamic list by property**.
|
||||
1. To add a target, in the "Targeting criteria" section, select **Add a target** {% octicon "triangle-down" aria-hidden="true" %}, then click **Include by property** or **Exclude by property**.
|
||||
1. In the modal dialog that appears, select a custom or system property from the dropdown menu, then select a value for the property.
|
||||
1. Click **Add target**.
|
||||
|
|
@ -38,5 +38,5 @@ You can target repositories in your organization by custom properties. For more
|
|||
|
||||
#### Targeting select repositories in your organization
|
||||
|
||||
1. To target a static, manually selected list of repositories in your organization, in the "Target repositories" section, select {% octicon "goal" aria-hidden="true" %} **Target: REPOSITORIES**, then click **Select repositories**.
|
||||
1. To select repositories to target, in the "Targeting criteria" section, select {% octicon "repo" aria-hidden="true" %} **Select repositories**, then search for the name of each repository you would like to target. Select each repository from the search results.
|
||||
1. To target a static, manually selected list of repositories in your organization, in the "Target repositories" section, select **{% octicon "goal" aria-hidden="true" %} Target: REPOSITORIES**, then click **Select repositories**.
|
||||
1. To select repositories to target, in the "Targeting criteria" section, select **{% octicon "repo" aria-hidden="true" %} Select repositories**, then search for the name of each repository you would like to target. Select each repository from the search results.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
1. Under your organization name, click {% ifversion projects-v2 %}{% octicon "table" aria-hidden="true" %}{% else %}{% octicon "project" aria-hidden="true" %}{% endif %} **Projects**.
|
||||
1. Under your organization name, click {% ifversion projects-v2 %}**{% octicon "table" aria-hidden="true" %}{% else %}{% octicon "project" aria-hidden="true" %}{% endif %} Projects**.
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under your organization name, click {% octicon "person" aria-hidden="true" %} **People**.
|
||||
1. Under your organization name, click **{% octicon "person" aria-hidden="true" %} People**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. At the top of the team's page, click {% octicon "comment-discussion" aria-hidden="true" %} **Discussions**.
|
||||
1. At the top of the team's page, click **{% octicon "comment-discussion" aria-hidden="true" %} Discussions**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
1. At the top of the team page, click {% octicon "organization" aria-hidden="true" %} **Members**.
|
||||
1. At the top of the team page, click **{% octicon "organization" aria-hidden="true" %} Members**.
|
||||
|
||||
{% ifversion global-nav-update %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
1. At the top of the team page, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
1. At the top of the team page, click **{% octicon "gear" aria-hidden="true" %} Settings**.
|
||||
|
||||
{% ifversion global-nav-update %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
1. Under your organization name, click {% octicon "people" aria-hidden="true" %} **Teams**.
|
||||
1. Under your organization name, click **{% octicon "people" aria-hidden="true" %} Teams**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization.
|
||||
1. Under your organization name, click the {% octicon "package" aria-hidden="true" %} **Packages** tab.
|
||||
1. Under your organization name, click the **{% octicon "package" aria-hidden="true" %} Packages** tab.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,4 +10,4 @@
|
|||
|
||||
|
||||
{% endif %}
|
||||
1. On your profile page, in the header, click the {% octicon "package" aria-hidden="true" %} **Packages** tab.
|
||||
1. On your profile page, in the header, click the **{% octicon "package" aria-hidden="true" %} Packages** tab.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. In the upper-right corner of {% data variables.product.prodname_dotcom %}, select your profile photo, then click{% ifversion fpt or ghec %} {% octicon "organization" aria-hidden="true" %}{% endif %} **Your organizations**.
|
||||
1. In the upper-right corner of {% data variables.product.prodname_dotcom %}, select your profile photo, then click{% ifversion fpt or ghec %} **{% octicon "organization" aria-hidden="true" %}{% endif %} Your organizations**.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click {% octicon "three-bars" aria-hidden="true" %} **Menu**.
|
||||
1. On the top-right side of the {% data variables.projects.projects_v1_board %}, click **{% octicon "three-bars" aria-hidden="true" %} Menu**.
|
||||
|
|
|
|||
|
|
@ -3,4 +3,4 @@
|
|||
|
||||
|
||||
|
||||
1. In the menu, click {% octicon "workflow" aria-hidden="true" %} **Workflows**.
|
||||
1. In the menu, click **{% octicon "workflow" aria-hidden="true" %} Workflows**.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
1. Under your organization name, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. Under your organization name, click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
|
||||
|
||||
1. Click **New project**.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
{% data reusables.profile.access_profile %}
|
||||
1. On your profile, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
1. On your profile, click **{% octicon "table" aria-hidden="true" %} Projects**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,6 @@
|
|||
> You cannot group by title, labels, reviewers, or linked pull requests.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "rows" aria-hidden="true" %} **Group by**.
|
||||
1. Click **{% octicon "rows" aria-hidden="true" %} Group by**.
|
||||
1. Click the field you want to group by.
|
||||
1. Optionally, to disable grouping, click {% octicon "x" aria-hidden="true" %} **No grouping** at the bottom of the list.
|
||||
1. Optionally, to disable grouping, click **{% octicon "x" aria-hidden="true" %} No grouping** at the bottom of the list.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
{% data reusables.projects.open-view-menu %}
|
||||
1. Under "Configuration", click {% octicon "note" aria-hidden="true" %} **Fields**.
|
||||
1. Under "Configuration", click **{% octicon "note" aria-hidden="true" %} Fields**.
|
||||
1. Select or deselect the fields you want to show or hide.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,6 @@ You can slice your items by a field to view a list of the field values in a sepa
|
|||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click **Slice by**.
|
||||
1. Click the field you want to slice by.
|
||||
1. Optionally, to disable slicing, click {% octicon "x" aria-hidden="true" %} **No slicing** at the bottom of the list.
|
||||
1. Optionally, to disable slicing, click **{% octicon "x" aria-hidden="true" %} No slicing** at the bottom of the list.
|
||||
|
||||
With the slice panel open, you can change the current field by using the menu at the top of the slice panel.
|
||||
|
|
|
|||
|
|
@ -3,5 +3,5 @@ You can configure a view to show the sum of one of more number fields, including
|
|||
In a board layout, field sums are displayed at the top of each column. In table and roadmap layouts, when you enable grouping by a field, field sums are included in each group's header.
|
||||
|
||||
{% data reusables.projects.open-view-menu %}
|
||||
1. Click {% octicon "number" aria-hidden="true" %} **Field sum**.
|
||||
1. Click **{% octicon "number" aria-hidden="true" %} Field sum**.
|
||||
1. Select the fields you want to include.
|
||||
|
|
|
|||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче