Merge branch 'main' into patch-2
This commit is contained in:
Ramya Parimi
@@ -97,7 +97,7 @@ jobs:
|
||||
For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae-next %}
|
||||
The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an enterprise, organization, or repository can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)."
|
||||
The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository,{% endif %} see {% ifversion not ghes %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)," {% endif %}"[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#setting-the-permissions-of-the-github_token-for-a-repository)."
|
||||
|
||||
| Scope | Default access<br>(permissive) | Default access<br>(restricted) | Maximum access<br>by forked repos |
|
||||
|---------------|-----------------------------|-----------------------------|--------------------------------|
|
||||
|
||||
@@ -75,7 +75,7 @@ Automatically detect security vulnerabilities and coding errors in new or modifi
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 %}
|
||||
{% ifversion fpt %}
|
||||
### Dependency review
|
||||
|
||||
Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
|
||||
|
||||
@@ -47,7 +47,7 @@ For more information, see "[About alerts for vulnerable dependencies](/code-secu
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 %}
|
||||
{% ifversion fpt %}
|
||||
|
||||
## Managing dependency review
|
||||
|
||||
|
||||
@@ -72,7 +72,7 @@ For more information, see "[About alerts for vulnerable dependencies](/code-secu
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 %}
|
||||
{% ifversion fpt %}
|
||||
## Managing dependency review
|
||||
|
||||
Dependency review lets you visualize dependency changes in pull requests before they are merged into your repository. Dependency review is available in all public repositories and in repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
|
||||
@@ -19,7 +19,7 @@ redirect_from:
|
||||
|
||||
Organization owners can manage which repositories a codespace can access.
|
||||
|
||||
By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust.
|
||||
By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit access to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust.
|
||||
|
||||
To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)."
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ redirect_from:
|
||||
---
|
||||
## About MakeCode Arcade
|
||||
|
||||
MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about online IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)."
|
||||
MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)."
|
||||
|
||||
{% data reusables.classroom.readme-contains-button-for-online-ide %}
|
||||
|
||||
|
||||
@@ -5,9 +5,9 @@ intro: 'You can help your students write, test, and debug code by preconfiguring
|
||||
versions:
|
||||
fpt: '*'
|
||||
children:
|
||||
- /integrate-github-classroom-with-an-online-ide
|
||||
- /integrate-github-classroom-with-an-ide
|
||||
- /about-using-makecode-arcade-with-github-classroom
|
||||
- /replit-with-github-classroom
|
||||
- /run-student-code-in-an-online-ide
|
||||
- /run-student-code-in-an-ide
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Integrate GitHub Classroom with an IDE
|
||||
shortTitle: Integrate with an IDE
|
||||
intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
redirect_from:
|
||||
- /education/manage-coursework-with-github-classroom/online-ide-integrations
|
||||
- /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide
|
||||
- /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide
|
||||
---
|
||||
## About integration with an IDE
|
||||
|
||||
{% data reusables.classroom.about-online-ides %}
|
||||
|
||||
After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary.
|
||||
|
||||
## Supported IDEs
|
||||
|
||||
{% data variables.product.prodname_classroom %} supports the following IDEs. You can learn more about the student experience for each IDE.
|
||||
|
||||
| IDE | More information |
|
||||
| :- | :- |
|
||||
| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
|
||||
| Visual Studio Code | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace |
|
||||
|
||||
We know cloud IDE integrations are important to your classroom and are working to bring more options.
|
||||
|
||||
## Configuring an IDE for an assignment
|
||||
|
||||
You can choose the IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
|
||||
|
||||
## Authorizing the OAuth app for an IDE
|
||||
|
||||
The first time you configure an assignment with an IDE, you must authorize the OAuth app for the IDE for your organization.
|
||||
|
||||
For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Integrate GitHub Classroom with an online IDE
|
||||
shortTitle: Integrate with an online IDE
|
||||
intro: 'You can preconfigure a supported online integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
redirect_from:
|
||||
- /education/manage-coursework-with-github-classroom/online-ide-integrations
|
||||
- /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide
|
||||
---
|
||||
## About integration with an online IDE
|
||||
|
||||
{% data reusables.classroom.about-online-ides %}
|
||||
|
||||
After a student accepts an assignment with an online IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary.
|
||||
|
||||
## Supported online IDE
|
||||
|
||||
{% data variables.product.prodname_classroom %} supports the following online IDE. You can learn more about the student experience for each IDE.
|
||||
|
||||
| IDE | More information |
|
||||
| :- | :- |
|
||||
| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
|
||||
|
||||
We know cloud IDE integrations are important to your classroom and are working to bring more options.
|
||||
|
||||
## Configuring an online IDE for an assignment
|
||||
|
||||
You can choose the online IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an online IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
|
||||
|
||||
## Authorizing the OAuth app for an online IDE
|
||||
|
||||
The first time you configure an assignment with an online IDE, you must authorize the OAuth app for the online IDE for your organization.
|
||||
|
||||
For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
|
||||
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: Run student code in an IDE
|
||||
intro: You can run the code from a student assignment within the integrated development environment (IDE) that you configured for the assignment.
|
||||
versions:
|
||||
fpt: '*'
|
||||
redirect_from:
|
||||
- /education/manage-coursework-with-github-classroom/running-student-code
|
||||
- /education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide
|
||||
- /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-online-ide
|
||||
shortTitle: Run code in IDE
|
||||
---
|
||||
|
||||
## About student code and IDEs
|
||||
|
||||
If you configure an integrated development environment (IDE) for an assignment, you can run the code within the IDE. You don't need to clone the assignment repository to your computer.
|
||||
|
||||
For more information about IDEs, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)."
|
||||
|
||||
## Running student code in the IDE
|
||||
|
||||
{% data reusables.classroom.sign-into-github-classroom %}
|
||||
{% data reusables.classroom.click-classroom-in-list %}
|
||||
{% data reusables.classroom.click-assignment-in-list %}
|
||||
1. To the right of the submission, click **View IDE**.
|
||||
|
||||
@@ -1,23 +0,0 @@
|
||||
---
|
||||
title: Run student code in an online IDE
|
||||
intro: You can run the code from a student assignment within the online integrated development environment (IDE) that you configured for the assignment.
|
||||
versions:
|
||||
fpt: '*'
|
||||
redirect_from:
|
||||
- /education/manage-coursework-with-github-classroom/running-student-code
|
||||
- /education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide
|
||||
shortTitle: Online IDE
|
||||
---
|
||||
## About student code and online IDEs
|
||||
|
||||
If you configure an online integrated development environment (IDE) for an assignment, you can run the code within the online IDE. You don't need to clone the assignment repository to your computer.
|
||||
|
||||
For more information about online IDEs, see "[Integrate {% data variables.product.prodname_classroom %} with an online IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide)."
|
||||
|
||||
## Running student code in the online IDE
|
||||
|
||||
{% data reusables.classroom.sign-into-github-classroom %}
|
||||
{% data reusables.classroom.click-classroom-in-list %}
|
||||
{% data reusables.classroom.click-assignment-in-list %}
|
||||
1. To the right of the submission, click **View IDE**.
|
||||
|
||||
@@ -80,7 +80,7 @@ If you've already created a group assignment for the classroom, you can reuse a
|
||||
{% data reusables.classroom.assignments-guide-intro-for-environment %}
|
||||
|
||||
- [Choosing a template repository](#choosing-a-template-repository)
|
||||
- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide)
|
||||
- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
|
||||
|
||||
### Choosing a template repository
|
||||
|
||||
@@ -88,7 +88,7 @@ By default, a new assignment will create an empty repository for each team that
|
||||
|
||||
{% data reusables.classroom.assignments-guide-choose-template-repository %}
|
||||
|
||||
### Choosing an online integrated development environment (IDE)
|
||||
### Choosing an integrated development environment (IDE)
|
||||
|
||||
{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
|
||||
|
||||
|
||||
@@ -60,7 +60,7 @@ Under "Individual or group assignment", select the drop-down menu, and click **I
|
||||
{% data reusables.classroom.assignments-guide-intro-for-environment %}
|
||||
|
||||
- [Choosing a template repository](#choosing-a-template-repository)
|
||||
- [Choosing an online integrated development environment (IDE)](#choosing-an-online-integrated-development-environment-ide)
|
||||
- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
|
||||
|
||||
### Choosing a template repository
|
||||
|
||||
@@ -70,7 +70,7 @@ By default, a new assignment will create an empty repository for each student on
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
|
||||
|
||||
### Choosing an online integrated development environment (IDE)
|
||||
### Choosing an integrated development environment (IDE)
|
||||
|
||||
{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
|
||||
|
||||
|
||||
@@ -7,101 +7,80 @@ redirect_from:
|
||||
- /github/using-git/caching-your-github-credentials-in-git
|
||||
- /github/getting-started-with-github/caching-your-github-credentials-in-git
|
||||
- /github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git
|
||||
intro: 'If you''re [cloning {% data variables.product.product_name %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), you can use a credential helper to tell Git to remember your credentials.'
|
||||
intro: 'If you''re [cloning {% data variables.product.product_name %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), we recommend you use Git Credential Manager Core (GCM Core) to remember your credentials.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
shortTitle: Caching credentials
|
||||
---
|
||||
If you clone {% data variables.product.product_name %} repositories using SSH, then you authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)."
|
||||
|
||||
{% mac %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tips:**
|
||||
|
||||
- You need Git **1.7.10** or newer to use the osxkeychain credential helper.
|
||||
- If you installed Git using [Homebrew](http://brew.sh/), the `osxkeychain helper` will already be installed.
|
||||
- If you're running Mac OS X 10.7 and above and you installed Git through Apple's Xcode Command Line Tools, then `osxkeychain helper` is automatically included in your Git installation.
|
||||
**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
Install Git and the `osxkeychain helper` and tell Git to use it.
|
||||
[Git Credential Manager Core](https://github.com/microsoft/Git-Credential-Manager-Core) (GCM Core) is our recommended way to store your credentials securely and connect to GitHub over HTTPS. With GCM Core, you don't have to manually [create and store a PAT](/github/authenticating-to-github/creating-a-personal-access-token), as GCM Core manages authentication on your behalf, including 2FA (two-factor authentication).
|
||||
|
||||
1. Find out if Git and the `osxkeychain helper` are already installed:
|
||||
```shell
|
||||
$ git credential-osxkeychain
|
||||
# Test for the cred helper
|
||||
> Usage: git credential-osxkeychain <get|store|erase>
|
||||
```
|
||||
2. If the `osxkeychain helper` isn't installed and you're running OS X version 10.9 or above, your computer will prompt you to download it as a part of the Xcode Command Line Tools:
|
||||
```shell
|
||||
$ git credential-osxkeychain
|
||||
> xcode-select: note: no developer tools were found at '/Applications/Xcode.app',
|
||||
> requesting install. Choose an option in the dialog to download the command line developer tools.
|
||||
```
|
||||
{% mac %}
|
||||
|
||||
Alternatively, you can install Git and the `osxkeychain helper` by using [Homebrew](http://brew.sh/):
|
||||
1. Install Git using [Homebrew](https://brew.sh/):
|
||||
```shell
|
||||
$ brew install git
|
||||
```
|
||||
|
||||
4. Tell Git to use `osxkeychain helper` using the global `credential.helper` config:
|
||||
2. Install GCM Core using Homebrew:
|
||||
```shell
|
||||
$ git config --global credential.helper osxkeychain
|
||||
# Set git to use the osxkeychain credential helper
|
||||
$ brew tap microsoft/git
|
||||
$ brew install --cask git-credential-manager-core
|
||||
```
|
||||
For MacOS, you don't need to run `git config` because GCM Core automatically configures Git for you.
|
||||
|
||||
The next time you clone an HTTPS URL that requires authentication, Git will prompt you for your username and password. {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
{% data reusables.gcm-core.next-time-you-clone %}
|
||||
|
||||
Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. You won't be required to type your credentials in to Git again unless you change your credentials.
|
||||
Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
{% tip %}
|
||||
1. Install Git for Windows, which includes GCM Core. For more information, see "[Git for Windows releases](https://github.com/git-for-windows/git/releases/latest)" from its [releases page](https://github.com/git-for-windows/git/releases/latest).
|
||||
|
||||
**Tip:** You need Git **1.7.10** or newer to use the credential helper.
|
||||
We recommend always installing the latest version. At a minimum, install version 2.29 or higher, which is the first version offering OAuth support for GitHub.
|
||||
|
||||
{% endtip %}
|
||||
{% data reusables.gcm-core.next-time-you-clone %}
|
||||
|
||||
You can also install a native Git shell, such as [Git for Windows](https://git-for-windows.github.io/). With Git for Windows, running the following in the command line will store your credentials:
|
||||
Once you've authenticated successfully, your credentials are stored in the Windows credential manager and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
|
||||
|
||||
```shell
|
||||
$ git config --global credential.helper wincred
|
||||
```
|
||||
<br>
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest).
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
{% linux %}
|
||||
|
||||
{% tip %}
|
||||
For Linus, Install Git and GCM Core, then configure Git to use GCM Core.
|
||||
|
||||
**Tip:** You need Git **1.7.10** or newer to use the credential helper.
|
||||
1. Install Git from your distro's packaging system. Instructions will vary depending on the flavor of Linux you run.
|
||||
|
||||
{% endtip %}
|
||||
2. Install GCM Core. See the [instructions in the GCM Core repo](https://github.com/microsoft/Git-Credential-Manager-Core#linux-install-instructions), as they'll vary depending on the flavor of Linux you run.
|
||||
|
||||
Turn on the credential helper so that Git will save your password in memory for some time. By default, Git will cache your password for 15 minutes.
|
||||
3. Configure Git to use GCM Core. There are several backing stores that you may choose from, so see the GCM Core docs to complete your setup. For more information, see "[GCM Core Linux](https://aka.ms/gcmcore-linuxcredstores)."
|
||||
|
||||
1. In Terminal, enter the following:
|
||||
```shell
|
||||
$ git config --global credential.helper cache
|
||||
# Set git to use the credential memory cache
|
||||
```
|
||||
2. To change the default password cache timeout, enter the following:
|
||||
```shell
|
||||
$ git config --global credential.helper 'cache --timeout=3600'
|
||||
# Set the cache to timeout after 1 hour (setting is in seconds)
|
||||
```
|
||||
{% data reusables.gcm-core.next-time-you-clone %}
|
||||
|
||||
Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
|
||||
|
||||
For more options for storing your credentials on Linux, see [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) in Pro Git.
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
## Further reading
|
||||
<br>
|
||||
|
||||
- "[Updating credentials from the OSX Keychain](/articles/updating-credentials-from-the-osx-keychain/)"
|
||||
- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
|
||||
For more information or to report issues with GCM Core, see the official GCM Core docs at "[Git Credential Manager Core](https://github.com/microsoft/Git-Credential-Manager-Core)."
|
||||
|
||||
@@ -13,6 +13,14 @@ versions:
|
||||
ghae: '*'
|
||||
shortTitle: macOS Keychain credentials
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a PAT using the `osxkeychain` helper that is built-in to macOS.
|
||||
|
||||
We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager Core](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM Core) instead. GCM Core can manage authentication on your behalf (no more manual PATs) including 2FA (two-factor auth).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.user_settings.password-authentication-deprecation %}
|
||||
|
||||
## Updating your credentials via Keychain Access
|
||||
|
||||
@@ -48,6 +48,8 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
|
||||
$ git remote set-url origin <em>new_url</em>
|
||||
```
|
||||
|
||||
- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)."
|
||||
|
||||
For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
|
||||
|
||||
### Repository transfers and organizations
|
||||
|
||||
@@ -24,6 +24,13 @@ $ ssh -T -ai <em>~/.ssh/id_rsa</em> git@{% data variables.command_line.codeblock
|
||||
|
||||
The *username* in the response is the {% data variables.product.product_name %} account that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a [*deploy key*](/guides/managing-deploy-keys#deploy-keys).
|
||||
|
||||
|
||||
To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option:
|
||||
|
||||
```shell
|
||||
$ ssh -v -o "IdentitiesOnly=yes" -i <em>~/.ssh/id_rsa</em> git@{% data variables.command_line.codeblock %}
|
||||
```
|
||||
|
||||
## Fixing the issue
|
||||
|
||||
To resolve the issue, first remove the key from the other account or repository and then [add it to your account](/articles/adding-a-new-ssh-key-to-your-github-account).
|
||||
|
||||
@@ -47,7 +47,9 @@ You'll see updates in your news feed when a user you follow:
|
||||
- Opens an issue or pull request with "help wanted" or "good first issue" label on a repository you're watching.
|
||||
- Pushes commits to a repository you watch.{% ifversion fpt or ghes %}
|
||||
- Forks a public repository.{% endif %}
|
||||
- Publishes a new release.
|
||||
|
||||
You'll also see updates in your news feed when a repository you've starred has a new release and the release mentions another user.
|
||||
For more information about starring repositories and following people, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)" and "[Following people](/articles/following-people)."
|
||||
|
||||
## Exploring recommended repositories
|
||||
|
||||
@@ -32,7 +32,7 @@ For more information, see "[Verifying or approving a domain for your organizatio
|
||||
|
||||
Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. For more information about outside collaborators, see "[Permission levels for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)."
|
||||
|
||||
If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
|
||||
If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. {% ifversion fpt %}For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."{% endif %}
|
||||
|
||||
## Restricting email notifications
|
||||
|
||||
|
||||
@@ -21,10 +21,14 @@ shortTitle: Verify or approve a domain
|
||||
|
||||
## About domain verification
|
||||
|
||||
After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
|
||||
After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "<a href="/articles/upgrading-to-the-corporate-terms-of-service" class="dotcom-only">Upgrading to the Corporate Terms of Service</a>."
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
If your organization is owned by an enterprise account, a "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owners. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.organizations.verified-domains-details %}
|
||||
|
||||
On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
@@ -39,8 +43,12 @@ After you approve domains for your organization, you can restrict email notifica
|
||||
|
||||
Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
Enterprise owners can also approve additional domains for organizations owned by the enterprise. For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Verifying a domain for your organization
|
||||
|
||||
To verify a domain, you must have access to modify domain records with your domain hosting service.
|
||||
|
||||
@@ -28,6 +28,8 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. For more information, see "[Configuring autolinks to reference external resources](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)."
|
||||
|
||||
{% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API.
|
||||
|
||||
{% for operation in currentRestOperations %}
|
||||
{% if operation.subcategory == 'autolinks' %}{% include rest_operation %}{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
Reference in New Issue
Block a user