You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sharing-contributions-from-github-enterprise-server.md
-7
Original file line number
Diff line number
Diff line change
@@ -42,15 +42,8 @@ To share contributions from {% data variables.product.prodname_ghe_server %}, vi
42
42
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 %}).
43
43
1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
44
44
45
-
{% ifversion global-nav-update %}
46
-
47
45
48
46
49
-
{% else %}
50
-
51
-
52
-
53
-
{% endif %}
54
47
{% data reusables.github-connect.github-connect-tab-user-settings %}
55
48
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
56
49
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**.
Copy file name to clipboardexpand all lines: content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -278,10 +278,10 @@ For more information about the `run` keyword, see [AUTOTITLE](/actions/using-wor
278
278
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#.
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.
31
31
{% 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 %}
32
32
33
-
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 %}
33
+
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 %}
34
34
35
35
> [!NOTE]
36
36
> 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
66
66
*`@dependabot merge` merges the pull request once your CI tests have passed.
67
67
*`@dependabot rebase` rebases the pull request.
68
68
*`@dependabot recreate` recreates the pull request, overwriting any edits that have been made to the pull request.
69
-
*`@dependabot reopen` reopens the pull request if the pull request is closed.{% ifversion dependabot-version-updates-groups %}
70
-
*`@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 %}
69
+
*`@dependabot reopen` reopens the pull request if the pull request is closed.
70
+
*`@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.
71
71
*`@dependabot squash and merge` squashes and merges the pull request once your CI tests have passed.
72
72
73
73
{% 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.
Copy file name to clipboardexpand all lines: content/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop.md
{% data reusables.desktop.update-email-address %} For more information, see [AUTOTITLE](/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop).
18
18
19
-
{% ifversion repo-rules %}
20
-
21
19
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).
22
20
23
-
{% endif %}
24
-
25
21
## Choosing a branch and making changes
26
22
27
23
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.
Copy file name to clipboardexpand all lines: content/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop.md
-4
Original file line number
Diff line number
Diff line change
@@ -27,12 +27,8 @@ You can always create a branch in {% data variables.product.prodname_desktop %}
27
27
28
28
{% data reusables.desktop.protected-branches %}
29
29
30
-
{% ifversion repo-rules %}
31
-
32
30
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).
Copy file name to clipboardexpand all lines: content/desktop/making-changes-in-a-branch/pushing-changes-to-github-from-github-desktop.md
-4
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,8 @@ Before pushing changes, you should update your local branch to include any commi
19
19
20
20
{% data reusables.desktop.protected-branches %}
21
21
22
-
{% ifversion repo-rules %}
23
-
24
22
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).
25
23
26
-
{% endif %}
27
-
28
24
## Pushing changes to {% data variables.product.prodname_dotcom %}
Copy file name to clipboardexpand all lines: content/get-started/using-github-docs/about-versions-of-github-docs.md
-7
Original file line number
Diff line number
Diff line change
@@ -33,13 +33,6 @@ You may use more than one {% data variables.product.company_short %} plan. For e
33
33
34
34
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 %}.
35
35
36
-
{% ifversion global-nav-update %}{% else %}
37
-
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.
38
-
39
-
40
-
41
-
{% endif %}
42
-
43
36
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).
44
37
45
38
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).
Copy file name to clipboardexpand all lines: content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout.md
-8
Original file line number
Diff line number
Diff line change
@@ -50,14 +50,10 @@ In the board layout, you can choose which columns to display. The available colu
50
50
51
51
1. Select the columns you want to show.
52
52
53
-
{% ifversion projects-v2-slice-panel %}
54
-
55
53
## Slicing by field values
56
54
57
55
{% data reusables.projects.customize.slice-panel %}
58
56
59
-
{% endif %}
60
-
61
57
## Sorting by field values
62
58
63
59
You can sort items by a field value.
@@ -67,8 +63,6 @@ You can sort items by a field value.
67
63
68
64
{% data reusables.projects.customize.sort %}
69
65
70
-
{% ifversion projects-v2-swimlanes %}
71
-
72
66
## Grouping by field values
73
67
74
68
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
77
71
78
72
{% data reusables.projects.customize.group-fields %}
Copy file name to clipboardexpand all lines: content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout.md
-4
Original file line number
Diff line number
Diff line change
@@ -33,14 +33,10 @@ You can group items by a custom field value. {% data reusables.projects.customiz
33
33
34
34
{% data reusables.projects.customize.group-fields %}
35
35
36
-
{% ifversion projects-v2-slice-panel %}
37
-
38
36
## Slicing by field values
39
37
40
38
{% data reusables.projects.customize.slice-panel %}
Copy file name to clipboardexpand all lines: content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
-4
Original file line number
Diff line number
Diff line change
@@ -21,12 +21,8 @@ In board layout, you can click on item data to filter for items with that value.
21
21
22
22
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.
23
23
24
-
{% ifversion projects-v2-insights %}
25
-
26
24
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).
27
25
28
-
{% endif %}
29
-
30
26
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."
31
27
32
28
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.
Copy file name to clipboardexpand all lines: content/issues/planning-and-tracking-with-projects/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -23,4 +23,4 @@ redirect_from:
23
23
24
24
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.
25
25
26
-
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.
26
+
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.
Copy file name to clipboardexpand all lines: content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ topics:
13
13
14
14
## About {% data variables.product.prodname_projects_v2 %}
15
15
16
-
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.
16
+
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.
17
17
18
18
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).
Copy file name to clipboardexpand all lines: content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
-7
Original file line number
Diff line number
Diff line change
@@ -45,15 +45,8 @@ You can create a branch in different ways on {% data variables.product.github %}
45
45
{% else %}
46
46
1. Select the branch selector dropdown menu.
47
47
48
-
{% ifversion global-nav-update %}
49
-
50
48
51
49
52
-
{% else %}
53
-
54
-
55
-
56
-
{% endif %}
57
50
{% endif %}
58
51
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.
59
52
1. In the "Find or create a branch..." text field, type a unique name for your new branch, then click **Create branch**.
0 commit comments