|
79 | 79 | description: A movable square within a project board associated with an issue or pull request. |
80 | 80 | - term: check |
81 | 81 | description: >- |
82 | | - A check is a type of status check on {% data variables.product.product_name %}. See "[Status checks](#status-checks)." |
| 82 | + A check is a type of status check on {% data variables.product.product_name %}. See [Status checks](#status-checks). |
83 | 83 | - term: checkout |
84 | 84 | description: >- |
85 | 85 | You can use `git checkout` on the command line to create a new branch, change your current working branch to a different branch, or even to switch to a different version of a file from a different branch with `git checkout [branchname] [path to file]`. The "checkout" action updates all or part of the working tree with a tree object or |
|
95 | 95 | - term: clean |
96 | 96 | description: >- |
97 | 97 | A working tree is clean if it corresponds to the revision referenced by the |
98 | | - current HEAD. Also see "[dirty](#dirty)." |
| 98 | + current HEAD. Also see [dirty](#dirty). |
99 | 99 | - term: clone |
100 | 100 | description: >- |
101 | 101 | A clone is a copy of a repository that lives on your computer instead of on |
|
156 | 156 | - term: contributions |
157 | 157 | description: >- |
158 | 158 | Specific activities on GitHub that will: |
159 | | - - Add a square to a user's contribution graph: "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile#what-counts-as-a-contribution)" |
160 | | - - Add activities to a user's timeline on their profile: "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile#contribution-activity)" |
| 159 | + - Add a square to a user's contribution graph: [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile#what-counts-as-a-contribution) |
| 160 | + - Add activities to a user's timeline on their profile: [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile#contribution-activity) |
161 | 161 | - term: contributor |
162 | 162 | description: >- |
163 | 163 | A contributor is someone who does not have collaborator access to a repository but has contributed to a project and had a pull request they opened merged into the repository. |
|
173 | 173 | description: Used in command lines or scripts to transfer data. |
174 | 174 | - term: dashboard |
175 | 175 | description: >- |
176 | | - Your personal dashboard is the main hub of your activity on GitHub. From your personal dashboard, you can keep track of issues and pull requests you're following or working on, navigate to your top repositories and team pages, and learn about recent activity in repositories you're watching or participating in. You can also discover new repositories, which are recommended based on users you're following and repositories you have starred. To only view activity for a specific organization, visit your organization's dashboard. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard)" or "[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard)." |
| 176 | + Your personal dashboard is the main hub of your activity on GitHub. From your personal dashboard, you can keep track of issues and pull requests you're following or working on, navigate to your top repositories and team pages, and learn about recent activity in repositories you're watching or participating in. You can also discover new repositories, which are recommended based on users you're following and repositories you have starred. To only view activity for a specific organization, visit your organization's dashboard. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard) or [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard). |
177 | 177 | - term: default branch |
178 | 178 | description: >- |
179 | 179 | The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called `main`, and is often the default branch. |
|
337 | 337 | that they configure and control. |
338 | 338 | - term: integration |
339 | 339 | description: >- |
340 | | - A third-party application that integrates with GitHub. These are often {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_actions %}, or custom actions. For more information, see "[AUTOTITLE](/get-started/exploring-integrations/about-building-integrations)." |
| 340 | + A third-party application that integrates with GitHub. These are often {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_actions %}, or custom actions. For more information, see [AUTOTITLE](/get-started/exploring-integrations/about-building-integrations). |
341 | 341 | - term: issue |
342 | 342 | description: >- |
343 | 343 | Issues are suggested improvements, tasks or questions related to the |
|
553 | 553 | Pull refers to when you are fetching in changes and merging them. For |
554 | 554 | instance, if someone has edited the remote file you're both working on, |
555 | 555 | you'll want to pull in those changes to your local copy so that it's up to |
556 | | - date. See also "[fetch](#fetch)." |
| 556 | + date. See also [fetch](#fetch). |
557 | 557 | - term: pull access |
558 | 558 | description: A synonym for read access. |
559 | 559 | - term: pull request |
|
673 | 673 | days. |
674 | 674 | - term: server-to-server request |
675 | 675 | description: >- |
676 | | - An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via the GitHub API. For more information, see "[AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app-installation)." See also, "[user-to-server request](#user-to-server-request)." |
| 676 | + An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via the GitHub API. For more information, see [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app-installation). See also, [user-to-server request](#user-to-server-request). |
677 | 677 | - term: service hook |
678 | 678 | description: >- |
679 | 679 | Also called "webhook." Webhooks provide a way for notifications to be |
|
700 | 700 | conditions set for the repository you're contributing to. |
701 | 701 | - term: status checks |
702 | 702 | description: >- |
703 | | - Status checks are external processes, such as continuous integration builds, which run for each commit you make in a repository. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." |
| 703 | + Status checks are external processes, such as continuous integration builds, which run for each commit you make in a repository. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks). |
704 | 704 | - term: star |
705 | 705 | description: >- |
706 | 706 | A bookmark or display of appreciation for a repository. Stars are a manual |
|
762 | 762 | description: A user's handle on GitHub. |
763 | 763 | - term: user-to-server request |
764 | 764 | description: >- |
765 | | - An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see "[AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user)." See also, "[server-to-server request](#server-to-server-request)." |
| 765 | + An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-with-a-github-app-on-behalf-of-a-user). See also, [server-to-server request](#server-to-server-request). |
766 | 766 | - term: visible team |
767 | 767 | description: A team that can be viewed and @mentioned by every organization member. |
768 | 768 | - term: watch |
|
0 commit comments