Fix initial errors identified when trying Vale (#17608)
* Fix errors in education product * Fix errors in admin configuration docs * Fix a few stray errors * This works as is * Sundry fixes picked up by Vale * Another batch * Today's batch of content fixes * Sundry fixes * More small updates * Don't introduce a typo when we're trying to fix them * Update content/admin/authentication/using-ldap.md Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Laura Coursen <lecoursen@github.com>
This commit is contained in:
Emily Gould
@@ -29,7 +29,7 @@ You can choose which repositories should have access to each secret. Then, you c
|
||||
1. To the right of "Codespaces secrets", click **New secret**.
|
||||
|
||||
1. Under "Name", type a name for your secret.
|
||||
|
||||
|
||||
{% data reusables.user_settings.codespaces-secret-value %}
|
||||
{% data reusables.user_settings.codespaces-secret-repository-access %}
|
||||
1. Click **Add secret**.
|
||||
|
||||
@@ -39,12 +39,12 @@ After you connect your {% data variables.product.product_name %} account to the
|
||||
### Opening a codespace in {% data variables.product.prodname_vscode %}
|
||||
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
2. Under Codespaces, click the codespace you want to develop in.
|
||||
2. Under "Codespaces", click the codespace you want to develop in.
|
||||
3. Click the Connect to Codespace icon.
|
||||
|
||||
|
||||
### Deleting a codespace in {% data variables.product.prodname_vscode %}
|
||||
|
||||
1. Under Codespaces, right-click the codespace you want to delete.
|
||||
1. Under "Codespaces", right-click the codespace you want to delete.
|
||||
2. In the drop-down menu, click **Delete Codespace**.
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ versions:
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### About Codespaces in {% data variables.product.prodname_vs %}
|
||||
### About codespaces in {% data variables.product.prodname_vs %}
|
||||
|
||||
You can create a codespace in {% data variables.product.prodname_vs %} to develop applications in a Windows environment. When you use a codespace in {% data variables.product.prodname_vs %}, you can browse source code, build solutions, and commit changes to your repository.
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ You can store a variety of projects in {% data variables.product.product_name %}
|
||||
|
||||
{% elsif enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
|
||||
|
||||
You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
|
||||
You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -58,7 +58,7 @@ When you created your new repository, you initialized it with a *README* file. *
|
||||
Let's commit a change to the *README* file.
|
||||
|
||||
1. In your repository's list of files, click ***README.md***.
|
||||
|
||||
|
||||
2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}.
|
||||
3. On the **Edit file** tab, type some information about yourself.
|
||||
|
||||
|
||||
@@ -25,11 +25,11 @@ For example, you can use forks to propose changes related to fixing a bug. Rathe
|
||||
|
||||
Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](http://opensource.org/about)" on the Open Source Initiative.
|
||||
|
||||
For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
|
||||
For more information about applying open source principles to your organization's development work on {% data variables.product.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](http://choosealicense.com/)" at choosealicense.
|
||||
When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](http://choosealicense.com/)" at choosealicense.com.
|
||||
|
||||
{% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %}
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ authors:
|
||||
|
||||
### Using Git
|
||||
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit ebook](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator.
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator.
|
||||
|
||||
### Using {% data variables.product.product_name %}
|
||||
|
||||
|
||||
@@ -161,8 +161,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
||||
|<kbd>command + space </kbd> or <kbd>control + space</kbd> | In the workflow editor, get suggestions for your workflow file.
|
||||
|<kbd>g</kbd> <kbd>f</kbd> | Go to the workflow file
|
||||
|<kbd>shift + t</kbd> or <kbd>T</kbd> | Toggle timestamps in logs
|
||||
|<kbd>shift + f</kbd> or <kbd>F</kbd> | Toggle fullscreen logs
|
||||
|<kbd>esc</kbd> | Exit fullscreen logs
|
||||
|<kbd>shift + f</kbd> or <kbd>F</kbd> | Toggle full-screen logs
|
||||
|<kbd>esc</kbd> | Exit full-screen logs
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ If you're having connectivity problems on your company or organization's network
|
||||
### Troubleshooting the captcha
|
||||
|
||||
If you're unable to verify with the captcha:
|
||||
- Ensure javascript is enabled on your browser.
|
||||
- Ensure JavaScript is enabled on your browser.
|
||||
- Ensure your browser is supported. If your browser isn't supported, upgrade your browser or install a supported browser. For a list of supported browsers, see "[Supported browsers](/articles/supported-browsers)."
|
||||
- Ensure your network configuration is not blocking https://octocaptcha.com/ or https://arkoselabs.com/. If you're behind a corporate firewall, contact your IT administrator to allow those domains. To verify access to these domains, visit https://octocaptcha.com/test and ensure the text "Connection successfully made!" is displayed, then visit https://client-demo.arkoselabs.com/github and ensure you are able to load the captcha.
|
||||
- Ensure your browser does not have plug-ins or extensions that may be interfering with GitHub. If so, temporarily disable the plug-ins or extensions during captcha verification.
|
||||
|
||||
@@ -54,11 +54,11 @@ Your contributions calendar shows your contribution activity.
|
||||
#### Viewing contributions from specific times
|
||||
|
||||
- Click on a day's square to show the contributions made during that 24-hour period.
|
||||
- Press *Shift* and click on another day's square to show contributions made during that timespan.
|
||||
- Press *Shift* and click on another day's square to show contributions made during that time span.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger timespan, we will only display one month of contributions.
|
||||
**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger time span, we will only display one month of contributions.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -50,7 +50,7 @@ Before you can sponsor an account, you must have a verified email address. For m
|
||||
1. Navigate to your sponsorship dashboard for the account.
|
||||
- To sponsor a developer, under the developer's name, click **Sponsor**.
|
||||
|
||||
- To sponsor an organization, to the right of the the organization's name, click **Sponsor**.
|
||||
- To sponsor an organization, to the right of the organization's name, click **Sponsor**.
|
||||
|
||||
1. Optionally, on the right side of the page, to sponsor the account on behalf of your organization, use the **Sponsor as** drop-down menu, and click the organization.
|
||||
|
||||
|
||||
@@ -30,5 +30,5 @@ You can export your sponsorship transactions by month. {% data variables.product
|
||||
{% data reusables.sponsors.activity-tab %}
|
||||
1. Click {% octicon "download" aria-label="The download icon" %} **Export**.
|
||||
|
||||
1. Choose a timeframe and a format for the data you'd like to export, then click **Start export**.
|
||||
1. Choose a time frame and a format for the data you'd like to export, then click **Start export**.
|
||||
|
||||
@@ -17,7 +17,7 @@ versions:
|
||||
Sometimes, {% data variables.product.prodname_pages %} will not attempt to build your site after you push changes to your site's publishing source.{% if currentVersion == "free-pro-team@latest" %}
|
||||
- The person who pushed the changes hasn't verified their email address. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %}
|
||||
- You're pushing with a deploy key. If you want to automate pushes to your site's repository, you can set up a machine user instead. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#machine-users)."
|
||||
- You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safelist. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation.
|
||||
- You're using a CI service that isn't configured to build your publishing source. For example, Travis CI won't build the `gh-pages` branch unless you add the branch to a safe list. For more information, see "[Customizing the build](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" on Travis CI, or your CI service's documentation.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user