Deprecate some missed 3.11 content (#54546)
This commit is contained in:
@@ -42,15 +42,8 @@ To share contributions from {% data variables.product.prodname_ghe_server %}, vi
|
||||
1. Sign in to both your user account on {% data variables.product.prodname_ghe_cloud %} **and** your user account on {% data variables.product.prodname_ghe_cloud %} ({% data variables.product.prodname_dotcom_the_website %}{% ifversion ghecom-github-connect %} or {% data variables.enterprise.data_residency_site %}{% endif %}).
|
||||
1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
|
||||
|
||||
{% ifversion global-nav-update %}
|
||||
|
||||

|
||||
|
||||
{% else %}
|
||||
|
||||

|
||||
|
||||
{% endif %}
|
||||
{% data reusables.github-connect.github-connect-tab-user-settings %}
|
||||
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
|
||||
1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghecom-github-connect %} or {% data variables.enterprise.data_residency_site %}{% endif %} account, then click **Authorize**.
|
||||
|
||||
@@ -278,10 +278,10 @@ For more information about the `run` keyword, see [AUTOTITLE](/actions/using-wor
|
||||
For repositories with multiple compiled languages, you can specify language-specific build commands. For example, if your repository contains C/C++, C# and Java, you might want to provide manual build steps for one language (here Java). This specifies build steps for Java while still using `autobuild` for C/C++ and C#.
|
||||
|
||||
```yaml
|
||||
- if: matrix.language == {% ifversion codeql-language-identifiers-311 %}'c-cpp'{% else %}'cpp'{% endif %} || matrix.language == 'csharp'
|
||||
- if: matrix.language == 'c-cpp' || matrix.language == 'csharp'
|
||||
name: Autobuild
|
||||
uses: {% data reusables.actions.action-codeql-action-autobuild %}
|
||||
- if: matrix.language == {% ifversion codeql-language-identifiers-311 %}'java-kotlin'{% else %}'java'{% endif %}
|
||||
- if: matrix.language == 'java-kotlin'
|
||||
name: Build Java
|
||||
run: |
|
||||
make bootstrap
|
||||
|
||||
@@ -26,9 +26,8 @@ If you're using advanced setup and your workflow doesn't explicitly specify the
|
||||
# ...
|
||||
strategy:
|
||||
fail-fast: false
|
||||
matrix: {% ifversion codeql-language-identifiers-311 %}
|
||||
language: ['csharp', 'c-cpp', 'javascript-typescript'] {% else %}
|
||||
language: ['csharp', 'cpp', 'javascript'] {% endif %}
|
||||
matrix:
|
||||
language: ['csharp', 'c-cpp', 'javascript-typescript']
|
||||
|
||||
steps:
|
||||
# ...
|
||||
|
||||
@@ -30,7 +30,7 @@ shortTitle: Manage Dependabot PRs
|
||||
When {% data variables.product.prodname_dependabot %} raises a pull request, you're notified by your chosen method for the repository. Each pull request contains detailed information about the proposed change, taken from the package manager. These pull requests follow the normal checks and tests defined in your repository.
|
||||
{% ifversion fpt or ghec %}In addition, where enough information is available, you'll see a compatibility score. This may also help you decide whether or not to merge the change. For information about this score, see [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates).{% endif %}
|
||||
|
||||
If you have many dependencies to manage, you may want to customize the configuration for each package manager so that pull requests have specific reviewers, assignees, and labels. {% ifversion dependabot-version-updates-groups %} You may also want to group sets of dependencies together, so that multiple dependencies are updated in a single pull request.{% endif %} For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/customizing-dependabot-prs){% ifversion dependabot-grouped-security-updates-config %} and [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#grouping-dependabot-updates-into-a-single-pull-request).{% else %} and [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#grouping-dependabot-security-updates-into-a-single-pull-request).{% endif %}
|
||||
If you have many dependencies to manage, you may want to customize the configuration for each package manager so that pull requests have specific reviewers, assignees, and labels. You may also want to group sets of dependencies together, so that multiple dependencies are updated in a single pull request. For more information, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/customizing-dependabot-prs){% ifversion dependabot-grouped-security-updates-config %} and [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#grouping-dependabot-updates-into-a-single-pull-request).{% else %} and [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#grouping-dependabot-security-updates-into-a-single-pull-request).{% endif %}
|
||||
|
||||
> [!NOTE]
|
||||
> If you don't interact with {% data variables.product.prodname_dependabot %} pull requests for a repository during a 90-day time period, {% data variables.product.prodname_dependabot %} considers your repository as inactive, and will automatically pause {% data variables.product.prodname_dependabot_updates %}. For more information about inactivity criteria, see [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#about-automatic-deactivation-of-dependabot-updates) and [AUTOTITLE](/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates#about-automatic-deactivation-of-dependabot-updates).
|
||||
@@ -66,8 +66,8 @@ You can use any of the following commands on a {% data variables.product.prodnam
|
||||
* `@dependabot merge` merges the pull request once your CI tests have passed.
|
||||
* `@dependabot rebase` rebases the pull request.
|
||||
* `@dependabot recreate` recreates the pull request, overwriting any edits that have been made to the pull request.
|
||||
* `@dependabot reopen` reopens the pull request if the pull request is closed.{% ifversion dependabot-version-updates-groups %}
|
||||
* `@dependabot show DEPENDENCY_NAME ignore conditions` retrieves information on the ignore conditions for the specified dependency, and comments on the pull request with a table that displays all ignore conditions for the dependency. For example, `@dependabot show express ignore conditions` would find all `ignore` conditions stored for the Express dependency, and comment on the pull request with that information.{% endif %}
|
||||
* `@dependabot reopen` reopens the pull request if the pull request is closed.
|
||||
* `@dependabot show DEPENDENCY_NAME ignore conditions` retrieves information on the ignore conditions for the specified dependency, and comments on the pull request with a table that displays all ignore conditions for the dependency. For example, `@dependabot show express ignore conditions` would find all `ignore` conditions stored for the Express dependency, and comment on the pull request with that information.
|
||||
* `@dependabot squash and merge` squashes and merges the pull request once your CI tests have passed.
|
||||
|
||||
{% data variables.product.prodname_dependabot %} will react with a "thumbs up" emoji to acknowledge the command, and may respond with a comment on the pull request. While {% data variables.product.prodname_dependabot %} usually responds quickly, some commands may take several minutes to complete if {% data variables.product.prodname_dependabot %} is busy processing other updates or commands.
|
||||
|
||||
@@ -16,12 +16,8 @@ shortTitle: Commit & review changes
|
||||
|
||||
{% data reusables.desktop.update-email-address %} For more information, see [AUTOTITLE](/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop).
|
||||
|
||||
{% ifversion repo-rules %}
|
||||
|
||||
Repository administrators can enable rulesets for a branch to enforce specific conventions when committing. For example, a ruleset can require a commit to be signed, or for an issue number to be referenced at the start of a commit message. {% data variables.product.prodname_desktop %} will display a warning and prevent committing if a commit does not follow the rulesets. For more information, see [AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Choosing a branch and making changes
|
||||
|
||||
1. [Create a new branch](/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking **{% octicon "git-branch" aria-hidden="true" %} Current Branch** on the toolbar and selecting the branch from the list.
|
||||
|
||||
@@ -27,12 +27,8 @@ You can always create a branch in {% data variables.product.prodname_desktop %}
|
||||
|
||||
{% data reusables.desktop.protected-branches %}
|
||||
|
||||
{% ifversion repo-rules %}
|
||||
|
||||
Repository administrators can also enable rulesets. Rulesets can be used to require specific branch names when creating a new branch, or to allow only users with bypass permissions to publish a new branch to the remote repository. {% data variables.product.prodname_desktop %} will show a warning and prevent the branch from being created if the branch does not follow the rulesets. For more information, see [AUTOTITLE](/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Creating a branch
|
||||
|
||||
> [!TIP]
|
||||
|
||||
@@ -19,12 +19,8 @@ Before pushing changes, you should update your local branch to include any commi
|
||||
|
||||
{% data reusables.desktop.protected-branches %}
|
||||
|
||||
{% ifversion repo-rules %}
|
||||
|
||||
Repository administrators can also enable rulesets for a branch, which will prevent a push from completing if a ruleset has not been followed. For example, a ruleset may require a specific branch naming convention, or an issue number at the start of a commit message. {% data variables.product.prodname_desktop %} will warn about rulesets to help prevent your branch from getting into a state where you would be unable to push your changes. For more information, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Pushing changes to {% data variables.product.prodname_dotcom %}
|
||||
|
||||
> [!NOTE]
|
||||
|
||||
@@ -33,13 +33,6 @@ You may use more than one {% data variables.product.company_short %} plan. For e
|
||||
|
||||
If you access {% data variables.product.prodname_dotcom %} at https://github.com, you're either using the features of a Free, Pro, or Team plan, or you're using {% data variables.product.prodname_ghe_cloud %}.
|
||||
|
||||
{% ifversion global-nav-update %}{% else %}
|
||||
In a wide browser window, there is no text that immediately follows the {% data variables.product.company_short %} logo on the left side of the header.
|
||||
|
||||

|
||||
|
||||
{% endif %}
|
||||
|
||||
On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. For more information, see [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts).
|
||||
|
||||
If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization).
|
||||
|
||||
@@ -50,14 +50,10 @@ In the board layout, you can choose which columns to display. The available colu
|
||||
|
||||
1. Select the columns you want to show.
|
||||
|
||||
{% ifversion projects-v2-slice-panel %}
|
||||
|
||||
## Slicing by field values
|
||||
|
||||
{% data reusables.projects.customize.slice-panel %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Sorting by field values
|
||||
|
||||
You can sort items by a field value.
|
||||
@@ -67,8 +63,6 @@ You can sort items by a field value.
|
||||
|
||||
{% data reusables.projects.customize.sort %}
|
||||
|
||||
{% ifversion projects-v2-swimlanes %}
|
||||
|
||||
## Grouping by field values
|
||||
|
||||
You can use a custom field value to group items and create horizontal sections on your board. These sections provide an additional way to organize and visually separate items. Additionally, horizontal grouping allows you to differentiate work according to work streams, team members, or varying levels of urgency or priority.
|
||||
@@ -77,8 +71,6 @@ You can use a custom field value to group items and create horizontal sections o
|
||||
|
||||
{% data reusables.projects.customize.group-fields %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Showing the sum of a number field
|
||||
|
||||
{% data reusables.projects.customize.sum %}
|
||||
|
||||
@@ -33,14 +33,10 @@ You can group items by a custom field value. {% data reusables.projects.customiz
|
||||
|
||||
{% data reusables.projects.customize.group-fields %}
|
||||
|
||||
{% ifversion projects-v2-slice-panel %}
|
||||
|
||||
## Slicing by field values
|
||||
|
||||
{% data reusables.projects.customize.slice-panel %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Reordering fields
|
||||
|
||||
You can change the order of fields.
|
||||
|
||||
@@ -21,12 +21,8 @@ In board layout, you can click on item data to filter for items with that value.
|
||||
|
||||
Using multiple filters will act as a logical AND filter. For example, `label:bug status:"In progress"` will return items with the `bug` label and the "In progress" status. You can also provide multiple values for the same field to act as a logical OR filter. For example, `label:bug,support` will return items with either the `bug` or `support` labels. {% data variables.product.prodname_projects_v2 %} does not currently support logical OR filters across multiple fields.
|
||||
|
||||
{% ifversion projects-v2-insights %}
|
||||
|
||||
The same filters are available for charts you create using insights for {% data variables.product.prodname_projects_v2 %}, allowing you to filter the data used to create your charts. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects).
|
||||
|
||||
{% endif %}
|
||||
|
||||
When you filter a view and then add an item, the filtered metadata will be applied to new item. For example, if you're filtering by `status:"In progress"` and you add an item, the new item will have its status set to "In progress."
|
||||
|
||||
You can use filters to produce views for very specific purposes. For example, you could use `assignee:@me status:todo last-updated:5days` to create a view of all work assigned to the current user, with the "todo" status, that hasn't been updated in the last five days. You could create a triage view by using a negative filter, such as `no:label no:assignee repo:octocat/game`, which would show items without a label and without an assignee that are located in the `octocat/game` repository.
|
||||
|
||||
@@ -23,4 +23,4 @@ redirect_from:
|
||||
|
||||
A project is an adaptable collection of items that you can view as a table, a kanban board, or a roadmap and that stays up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you note down.
|
||||
|
||||
You can create and customize multiple views by filtering, sorting, and grouping issues and pull requests,{% ifversion projects-v2-insights %} visualize work with configurable charts,{% endif %} and add custom fields to track metadata specific to your team. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
|
||||
You can create and customize multiple views by filtering, sorting, and grouping issues and pull requests, visualize work with configurable charts, and add custom fields to track metadata specific to your team. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
|
||||
|
||||
@@ -13,7 +13,7 @@ topics:
|
||||
|
||||
## About {% data variables.product.prodname_projects_v2 %}
|
||||
|
||||
A project is an adaptable spreadsheet, task-board, and road map that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests,{% ifversion projects-v2-insights %} visualize work with configurable charts,{% endif %} and add custom fields to track metadata specific to your team. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
|
||||
A project is an adaptable spreadsheet, task-board, and road map that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, visualize work with configurable charts, and add custom fields to track metadata specific to your team. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
|
||||
|
||||
To get started and create a project, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project). To learn more about the different layouts, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view).
|
||||
|
||||
|
||||
@@ -45,15 +45,8 @@ You can create a branch in different ways on {% data variables.product.github %}
|
||||
{% else %}
|
||||
1. Select the branch selector dropdown menu.
|
||||
|
||||
{% ifversion global-nav-update %}
|
||||
|
||||

|
||||
|
||||
{% else %}
|
||||
|
||||

|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
1. Optionally, if you want to create the new branch from a branch other than the default branch of the repository, click another branch, then select the branch dropdown menu again.
|
||||
1. In the "Find or create a branch..." text field, type a unique name for your new branch, then click **Create branch**.
|
||||
|
||||
@@ -12,7 +12,7 @@ topics:
|
||||
|
||||
{% data variables.product.prodname_dotcom %} code search lets you rapidly search, navigate and understand your code, your team's code, and the code of the open source community. This search engine is designed to be scalable, code-aware, and support searching code across {% data variables.product.prodname_dotcom %} using regular expressions, boolean operations, specialized qualifiers, and symbol search. For more information on the syntax of code search, see [AUTOTITLE](/search-github/github-code-search/understanding-github-code-search-syntax).
|
||||
|
||||
Code search is integrated with features in the search interface on {% data variables.product.prodname_dotcom %}, such as suggestions and completions. Your searches will be saved automatically and can be deleted at any time. On {% data variables.product.prodname_mobile %}, you can use the same methods to search through code {% ifversion global-code-search-mobile %}directly from the home screen{% else %} in a specific repository{% endif %}. For more information, see [AUTOTITLE](/search-github/github-code-search/using-github-code-search).
|
||||
Code search is integrated with features in the search interface on {% data variables.product.prodname_dotcom %}, such as suggestions and completions. Your searches will be saved automatically and can be deleted at any time. On {% data variables.product.prodname_mobile %}, you can use the same methods to search through code directly from the home screen. For more information, see [AUTOTITLE](/search-github/github-code-search/using-github-code-search).
|
||||
|
||||
{% data reusables.search.code-search-login-requirement %}
|
||||
|
||||
@@ -45,7 +45,7 @@ If you use the `path:` qualifier for a file that's in multiple repositories with
|
||||
|
||||
Code search supports searching for symbol definitions in code, such as function or class definitions, using the `symbol:` qualifier. However, note that the `symbol:` qualifier only searches for definitions and not references, and not all symbol types or languages are fully supported yet. For a list of what languages are supported, see [AUTOTITLE](/search-github/github-code-search/understanding-github-code-search-syntax#symbol-qualifier).
|
||||
|
||||
{% ifversion global-code-search-mobile %}On {% data variables.product.prodname_mobile %}, you can use code search directly from the home screen. For more information, see [AUTOTITLE](/search-github/github-code-search/using-github-code-search#using-github-code-search-on-github-mobile).{% endif %}
|
||||
On {% data variables.product.prodname_mobile %}, you can use code search directly from the home screen. For more information, see [AUTOTITLE](/search-github/github-code-search/using-github-code-search#using-github-code-search-on-github-mobile).
|
||||
|
||||
## Feedback and support
|
||||
|
||||
|
||||
@@ -84,16 +84,6 @@ On the search results view, you can navigate between different types of search r
|
||||
|
||||
## Using {% data variables.product.prodname_dotcom %} code search on {% data variables.product.prodname_mobile %}
|
||||
|
||||
{% ifversion global-code-search-mobile %}On {% data variables.product.prodname_mobile %}, you can use code search directly from the search bar in the home screen.{% else %} On {% data variables.product.prodname_mobile %}, you can navigate to a repository and use code search on the code in that repository.{% endif %} Code search on {% data variables.product.prodname_mobile %} uses the same syntax as code search on {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/search-github/github-code-search/about-github-code-search#limitations).
|
||||
|
||||
{% ifversion global-code-search-mobile %}
|
||||
On {% data variables.product.prodname_mobile %}, you can use code search directly from the search bar in the home screen. Code search on {% data variables.product.prodname_mobile %} uses the same syntax as code search on {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/search-github/github-code-search/about-github-code-search#limitations).
|
||||
|
||||
Once you start typing a search query, you will see a list of completions and suggestions that match your query. You can click on a suggestion to jump to a specific location. As you type more qualifiers, you will see more specific suggestions, such as code files you can jump to directly.
|
||||
|
||||
{% 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.
|
||||
{% data reusables.search.type-code-search-query-step %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
Reference in New Issue
Block a user