Merge branch 'main' into main
This commit is contained in:
Adam Ross Russell
2
.github/review-template.md
vendored
2
.github/review-template.md
vendored
@@ -1,7 +1,7 @@
|
||||
## Author self-review
|
||||
|
||||
- [ ] The changes in this PR meet the user experience and goals outlined in the content design plan.
|
||||
- [ ] I've compared my PR's source changes to staging and reviewed for versioning issues, redirects, the [style guide](https://github.com/github/docs/blob/main/contributing/content-style-guide.md), [content model](https://github.com/github/docs/blob/main/contributing/content-model.md), or [localization checklist](https://github.com/github/docs/blob/main/contributing/localization-checklist.md) rendering problems, typos, and wonky screenshots.
|
||||
- [ ] I've compared my PR's source changes to staging and reviewed for versioning issues, redirects, the [style guide](https://github.com/github/docs/blob/main/contributing/content-style-guide.md), [content model](https://github.com/github/docs/blob/main/contributing/content-model.md), or [translations guide for writers](https://github.com/github/docs/blob/main/contributing/translations/for-writers.md) rendering problems, typos, and wonky screenshots.
|
||||
- [ ] I've worked through build failures and tests are passing.
|
||||
- [ ] For REST API content, I've verified that endpoints, parameters, and responses are correct and work as expected and provided curl samples below.
|
||||
|
||||
|
||||
@@ -119,6 +119,9 @@ jobs:
|
||||
- name: Start the server in the background
|
||||
env:
|
||||
ENABLE_DEV_LOGGING: false
|
||||
# Makes it so that the React rendering of pages just does the
|
||||
# minimal needed to be able to extract the page text for search.
|
||||
MINIMAL_RENDER: true
|
||||
run: |
|
||||
npm run sync-search-server > /tmp/stdout.log 2> /tmp/stderr.log &
|
||||
|
||||
|
||||
3
.github/workflows/sync-search-pr.yml
vendored
3
.github/workflows/sync-search-pr.yml
vendored
@@ -67,6 +67,9 @@ jobs:
|
||||
- name: Start the server in the background
|
||||
env:
|
||||
ENABLE_DEV_LOGGING: false
|
||||
# Makes it so that the React rendering of pages just does the
|
||||
# minimal needed to be able to extract the page text for search.
|
||||
MINIMAL_RENDER: true
|
||||
run: |
|
||||
npm run sync-search-server > /tmp/stdout.log 2> /tmp/stderr.log &
|
||||
|
||||
|
||||
@@ -28,6 +28,24 @@ export const DefaultLayout = (props: Props) => {
|
||||
const router = useRouter()
|
||||
const metaDescription = page.introPlainText ? page.introPlainText : t('default_description')
|
||||
|
||||
// This is only true when we do search indexing which renders every page
|
||||
// just to be able to `cheerio` load the main body (and the meta
|
||||
// keywords tag).
|
||||
if (process.env.MINIMAL_RENDER) {
|
||||
return (
|
||||
<div>
|
||||
<Head>
|
||||
<title>{page.fullTitle}</title>
|
||||
{/* For local site search indexing */}
|
||||
{page.topics.length > 0 && <meta name="keywords" content={page.topics.join(',')} />}
|
||||
</Head>
|
||||
<main id="main-content" style={{ scrollMarginTop: '5rem' }}>
|
||||
{props.children}
|
||||
</main>
|
||||
</div>
|
||||
)
|
||||
}
|
||||
|
||||
return (
|
||||
<div className="d-lg-flex">
|
||||
<Head>
|
||||
|
||||
@@ -21,7 +21,7 @@ Use the official Octokit library, or choose between any of the available third p
|
||||
|
||||
- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
- **JavaScript** → [octokit.js](https://github.com/octokit/octokit.js)
|
||||
|
||||
## Third-party libraries
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ Here, you'll find additional information that might be helpful as you work on a
|
||||
- [content templates](./content-templates.md) - handy templates to get you started with a new article
|
||||
- [deployments](./deployments.md) - how our staging and production environments work
|
||||
- [liquid helpers](./liquid-helpers.md) - using liquid helpers for versioning in our docs
|
||||
- [localization checklist](./localization-checklist.md) - making sure your content is ready to be translated
|
||||
- [translations guide for writers](./translations/for-writers.md) - making sure your content is ready to be translated
|
||||
- [node versions](./node-versions.md) - our site runs on Node.js
|
||||
- [permalinks](./permalinks.md) - permalinks for article versioning
|
||||
- [redirects](./redirects.md) - configuring redirects in the site
|
||||
|
||||
@@ -7,7 +7,7 @@ For content changes, make sure that you:
|
||||
- [ ] Confirm that the changes meet the user experience and goals outlined in the content design plan (if there is one).
|
||||
- [ ] Compare your pull request's source changes to staging to confirm that the output matches the source and that everything is rendering as expected. This helps spot issues like typos, content that doesn't follow the style guide, or content that isn't rendering due to versioning problems. Remember that lists and tables can be tricky.
|
||||
- [ ] Review the content for technical accuracy.
|
||||
- [ ] Review the entire pull request using the [localization checklist](localization-checklist.md).
|
||||
- [ ] Review the entire pull request using the [translations guide for writers](./translations/for-writers.md).
|
||||
- [ ] Copy-edit the changes for grammar, spelling, and adherence to the [style guide](https://github.com/github/docs/blob/main/contributing/content-style-guide.md).
|
||||
- [ ] Check new or updated Liquid statements to confirm that versioning is correct.
|
||||
- [ ] If there are any failing checks in your PR, troubleshoot them until they're all passing.
|
||||
|
||||
19
contributing/translations/for-translators.md
Normal file
19
contributing/translations/for-translators.md
Normal file
@@ -0,0 +1,19 @@
|
||||
# Translation guide for translators
|
||||
|
||||
## Translated files
|
||||
We only translate:
|
||||
- all files `/content`
|
||||
- `/data/release-notes`
|
||||
- `/data/reusables`
|
||||
- `/data/variables` - **except** `/data/variables/product.yml`
|
||||
- `/data/glossaries/external.yml`
|
||||
- `/data/product-examples`
|
||||
|
||||
## Translation guidelines
|
||||
We do not accept translation changes from open source contributors.
|
||||
|
||||
- [ ] Lint all `*.yml` files before submitting to make sure they are valid YAML format.
|
||||
- [ ] Lint all frontmatter (between the triple dashes at the top of all `/content` files) to make sure they are valid YAML format.
|
||||
- [ ] Do not translate anything inside of Liquid tags, such as `{% data %}` or `{% ifversion ... %}`, `{% note %}` or `{{ someVariable }}`.
|
||||
- [ ] Be sure to translate the frontmatter properties `title`, `shortTitle`, `intro`, `permissions` but leave all other keys in each content `.md` file
|
||||
- [ ] For every `{% ifversion ... %}` there's a `{% endif %}` following it
|
||||
@@ -1,6 +1,6 @@
|
||||
# Localization Prep Checklist
|
||||
# Translations guide for writers
|
||||
|
||||
Use the following checklist to help make your files more translation-friendly. For additional information, refer to the [style guide](content-style-guide.md).
|
||||
Use the following checklist to help make your files more translation-friendly. For additional information, refer to the [style guide](../content-style-guide.md).
|
||||
|
||||
- [ ] Use examples that are generic and can be understood by most people.
|
||||
- [ ] Avoid controversial examples or culturally specific to a group.
|
||||
@@ -49,6 +49,7 @@ export default async function syncSearchIndexes({
|
||||
}
|
||||
})
|
||||
|
||||
let countRecordsTotal = 0
|
||||
// Build and validate all indices
|
||||
for (const languageCode of languagesToBuild) {
|
||||
for (const pageVersion of versionsToBuild) {
|
||||
@@ -63,7 +64,7 @@ export default async function syncSearchIndexes({
|
||||
// github-docs-dotcom-en, github-docs-2.22-en
|
||||
const indexName = `${namePrefix}-${indexVersion}-${languageCode}`
|
||||
|
||||
// The page version will be the new version, e.g., free-pro-team@latest, enterprise-server@2.22
|
||||
// The page version will be the new version, e.g., free-pro-team@latest, enterprise-server@3.7
|
||||
const records = await buildRecords(
|
||||
indexName,
|
||||
indexablePages,
|
||||
@@ -72,6 +73,7 @@ export default async function syncSearchIndexes({
|
||||
redirects,
|
||||
config
|
||||
)
|
||||
countRecordsTotal += records.length
|
||||
const fileWritten = await writeIndexRecords(indexName, records, outDirectory)
|
||||
console.log(`wrote records to ${fileWritten}`)
|
||||
}
|
||||
@@ -80,5 +82,11 @@ export default async function syncSearchIndexes({
|
||||
const tookSec = (t1.getTime() - t0.getTime()) / 1000
|
||||
|
||||
console.log('\nDone!')
|
||||
console.log(`Took ${tookSec.toFixed(1)} seconds`)
|
||||
console.log(`Took ${chalk.bold(formatSeconds(tookSec))}`)
|
||||
const rate = (countRecordsTotal / tookSec).toFixed(1)
|
||||
console.log(`Rate ~${chalk.bold(rate)} pages per second.`)
|
||||
}
|
||||
|
||||
function formatSeconds(seconds) {
|
||||
return new Date(seconds * 1000).toISOString().substr(11, 8)
|
||||
}
|
||||
|
||||
@@ -1091,6 +1091,7 @@ translations/ru-RU/content/repositories/releasing-projects-on-github/automatical
|
||||
translations/ru-RU/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
|
||||
translations/ru-RU/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
|
||||
translations/ru-RU/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
|
||||
translations/ru-RU/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md,rendering error
|
||||
translations/ru-RU/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md,rendering error
|
||||
translations/ru-RU/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
|
||||
translations/ru-RU/content/repositories/working-with-files/managing-files/navigating-files-with-the-new-code-view.md,broken liquid tags
|
||||
@@ -1272,7 +1273,6 @@ translations/ru-RU/data/reusables/enterprise-accounts/continue-verifying-domain.
|
||||
translations/ru-RU/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md,rendering error
|
||||
translations/ru-RU/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
|
||||
translations/ru-RU/data/reusables/enterprise-accounts/emu-cap-validates.md,rendering error
|
||||
translations/ru-RU/data/reusables/enterprise-accounts/emu-forks.md,rendering error
|
||||
translations/ru-RU/data/reusables/enterprise-accounts/emu-only-emails-within-the-enterprise-can-conflict.md,rendering error
|
||||
translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-follow.md,rendering error
|
||||
translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-fork.md,rendering error
|
||||
|
||||
|
@@ -16,9 +16,11 @@ topics:
|
||||
|
||||
## About forking
|
||||
|
||||
After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
|
||||
If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
|
||||
|
||||
Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
{% data reusables.repositories.fork-definition-long %}
|
||||
|
||||
You can contribute by submitting pull requests from your fork to the upstream repository. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
@@ -29,7 +31,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -40,7 +42,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -192,7 +194,7 @@ To do so, head on over to the repository on {% data variables.product.product_na
|
||||
|
||||
## Managing feedback
|
||||
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your changes exist in your fork. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
|
||||
|
||||
## Finding projects
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
- /articles/fork-a-repo
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/quickstart/fork-a-repo
|
||||
intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
|
||||
intro: A fork is a new repository that shares code and visibility settings with the original “upstream” repository.
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -21,7 +21,7 @@ topics:
|
||||
---
|
||||
## About forks
|
||||
|
||||
Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
{% data reusables.repositories.fork-definition-long %} For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
|
||||
|
||||
### Propose changes to someone else's project
|
||||
|
||||
@@ -47,20 +47,20 @@ When creating your public repository from a fork of someone's project, make sure
|
||||
|
||||
## Prerequisites
|
||||
|
||||
If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
|
||||
If you haven't yet, first set up Git and authentication with {% data variables.location.product_location %} from Git. For more information, see "[Set up Git](/articles/set-up-git)."
|
||||
|
||||
## Forking a repository
|
||||
|
||||
{% webui %}
|
||||
|
||||
You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
|
||||
|
||||
1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
|
||||
2. In the top-right corner of the page, click **Fork**.
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
**Note:** If you want to copy additional branches from the upstream repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -146,9 +146,9 @@ gh repo fork REPOSITORY --clone=true
|
||||
|
||||
{% enddesktop %}
|
||||
|
||||
## Configuring Git to sync your fork with the original repository
|
||||
## Configuring Git to sync your fork with the upstream repository
|
||||
|
||||
When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
|
||||
When you fork a project in order to propose changes to the upstream repository, you can configure Git to pull changes from the upstream repository into the local clone of your fork.
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -172,7 +172,7 @@ When you fork a project in order to propose changes to the original repository,
|
||||
$ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
|
||||
```
|
||||
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
|
||||
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the upstream repository as `upstream`.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
|
||||
@@ -208,7 +208,7 @@ gh repo fork REPOSITORY --remote-name "main-remote-repo"
|
||||
You can make any changes to a fork, including:
|
||||
|
||||
- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
|
||||
- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
- **Opening pull requests:** If you want to contribute back to the upstream repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
## Find another repository to fork
|
||||
Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
|
||||
|
||||
@@ -15,12 +15,12 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: Deleted or changes visibility
|
||||
ms.openlocfilehash: d52215a7406edc84bc71022517f848faa9e48600
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.openlocfilehash: 95296f33d9163cd1171481386efd0a2351095c39
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146332734'
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: '148191369'
|
||||
---
|
||||
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
|
||||
|
||||
@@ -32,7 +32,7 @@ ms.locfileid: '146332734'
|
||||
|
||||
## Удаление общедоступного репозитория
|
||||
|
||||
При удалении общедоступного репозитория одна из существующих общедоступных вилок становится новым родительским репозиторием. Все остальные репозитории ответвляются от этого нового родительского репозитория, и последующие запросы на вытягивание поступают в него.
|
||||
При удалении общедоступного репозитория одна из существующих общедоступных вилок выбирается в качестве нового вышестоящего репозитория. Все остальные репозитории удаляются из этого нового вышестоящего репозитория, и последующие запросы на вытягивание отправляются в этот новый вышестоящий репозиторий.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -44,9 +44,9 @@ ms.locfileid: '146332734'
|
||||
|
||||
## Преобразование общедоступного репозитория в частный
|
||||
|
||||
Если общедоступный репозиторий становится частным, его общедоступные вилки отделяются в новую сеть. Как и при удалении общедоступного репозитория, одна из существующих общедоступных вилок становится новым родительским репозиторием. Все остальные репозитории будут ответвляться от нее. Последующие запросы на вытягивание поступают в этот новый родительский репозиторий.
|
||||
Если общедоступный репозиторий становится частным, его общедоступные вилки отделяются в новую сеть. Как и при удалении общедоступного репозитория, одна из существующих общедоступных вилок выбирается в качестве нового вышестоящего репозитория, а все остальные репозитории удаляются из этого нового вышестоящего репозитория. Последующие запросы на вытягивание отправляются в этот новый вышестоящий репозиторий.
|
||||
|
||||
Иными словами, вилки общедоступного репозитория останутся общедоступными в отдельной сети репозиториев даже после того, как родительский репозиторий станет частным. Это позволяет владельцам вилок продолжать самостоятельную и совместную работу без перерывов. Если бы общедоступные вилки не были перенесены в отдельную сеть таким образом, их владельцам пришлось бы получать соответствующие [разрешения на доступ](/articles/access-permissions-on-github) для извлечения изменений и отправки запросов на вытягивание в родительский репозиторий (ставший частным), хотя эти разрешения раньше были не нужны.
|
||||
Иными словами, вилки общедоступного репозитория будут оставаться открытыми в отдельной сети репозитория даже после того, как вышестоящий репозиторий станет частным. Это позволяет владельцам вилок продолжать самостоятельную и совместную работу без перерывов. Если общедоступные вилки не были перемещены в отдельную сеть таким образом, владельцы этих вилок должны были бы получить соответствующие [разрешения на доступ](/articles/access-permissions-on-github) для извлечения изменений и отправки запросов на вытягивание в вышестоящий репозиторий (теперь частный), даже если раньше им не нужны эти разрешения.
|
||||
|
||||
{% ifversion ghes or ghae %} Если общедоступный репозиторий с анонимным доступом на чтение GIT становится частным, все его вилки утрачивают этот доступ и восстанавливается настройка "отключено" по умолчанию. Если вилки репозитория становятся общедоступными, администраторы репозитория могут повторно включить анонимный доступ на чтение GIT. Дополнительные сведения см. в разделе [Включение анонимного доступа на чтение в GIT для репозитория](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository).
|
||||
{% endif %}
|
||||
@@ -57,7 +57,7 @@ ms.locfileid: '146332734'
|
||||
|
||||
## Преобразование частного репозитория в общедоступный
|
||||
|
||||
Если частный репозиторий становится общедоступным, каждая из его частных вилок преобразуется в отдельный частный репозиторий и становится родительским репозиторием в новой собственной сети репозиториев. Частные вилки никогда не становятся общедоступными автоматически, так как могут содержать конфиденциальные фиксации, которые не должны находиться в открытом доступе.
|
||||
Если частный репозиторий становится общедоступным, каждая из его частных вилок превращается в автономный частный репозиторий и становится вышестоящей новой сетью репозитория. Частные вилки никогда не становятся общедоступными автоматически, так как могут содержать конфиденциальные фиксации, которые не должны находиться в открытом доступе.
|
||||
|
||||
### Удаление общедоступного репозитория
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Основные сведения о подключениях между репозиториями
|
||||
intro: 'Вы сможете лучше понять подключения между репозиториями, просмотрев сеть репозитория и вилки, а также проекты, которые зависят от репозитория.'
|
||||
title: Understanding connections between repositories
|
||||
intro: Use the network graph and forks list to understand fork networks.
|
||||
product: '{% data reusables.gated-features.repository-insights %}'
|
||||
redirect_from:
|
||||
- /articles/viewing-a-repository-s-network
|
||||
@@ -22,59 +22,57 @@ versions:
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: Connections between repositories
|
||||
ms.openlocfilehash: f1b92a62d0acf9f31a16ce1b7c57850b87c1bf9c
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147060069'
|
||||
---
|
||||
## Просмотр сети репозитория
|
||||
|
||||
На графе сети отображается история ветвей всей сети репозитория, включая ветви корневого репозитория и ветви вилок, содержащие уникальные для сети фиксации.
|
||||
## Viewing a repository's network
|
||||
|
||||
|
||||
The network graph displays the branch history of the entire repository network, including fork branches. This graph is a timeline of the most recent commits, and shows up to 100 of the most recently pushed-to branches. The first row references the date and the first column references the branch owner. Use arrow keys or other keyboard shortcuts to more easily navigate the graph. They are provided in the “Keyboard shortcuts available” pop up under the graph.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Совет.** Чтобы увидеть более старые ветви, нажмите и перетащите в пределах графа.
|
||||
**Tip:** To see older branches, click and drag within the graph.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Доступ к сетевому графу
|
||||
## Accessing the network graph
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. На левой боковой панели щелкните **Сеть**.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Network**.
|
||||
|
||||
|
||||
## Список вилок репозитория
|
||||
## Listing the forks of a repository
|
||||
|
||||
На графе "Элементы" отображаются все вилки репозитория.
|
||||
The Members graph displays all the forks of a repository.
|
||||
|
||||
Вилки перечислены в алфавитном порядке по имени пользователя, разветвившего репозиторий. Можно нажать имя пользователя, чтобы перейти на страницу профиля пользователя {% data variables.product.product_name %} или нажать имя вилки, чтобы перейти на конкретную вилку репозитория.
|
||||
Forks are listed alphabetically by the organization or username of the person who forked the repository. You can click on the organization or username to be redirected to the organization or user's {% data variables.product.product_name %} profile page or click on the fork name to be redirected to the specific fork of the repository.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Доступ к графу "Члены"
|
||||
### Accessing the Members graph
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. На левой боковой панели щелкните **Вилки**.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Forks**.
|
||||
|
||||
|
||||
## Просмотр зависимостей репозитория
|
||||
## Viewing the dependencies of a repository
|
||||
|
||||
Можно использовать граф зависимостей для изучения кода, от которого зависит репозиторий.
|
||||
You can use the dependency graph to explore the code your repository depends on.
|
||||
|
||||
Почти все программное обеспечение полагается на код, разработанный и поддерживаемый другими разработчиками, часто известный как цепочка поставок. Например, утилиты, библиотеки и платформы. Эти зависимости являются целочисленным элементом кода, и любые ошибки или уязвимости в них могут повлиять на код. Важно проверять и обслуживать эти зависимости.
|
||||
Almost all software relies on code developed and maintained by other developers, often known as a supply chain. For example, utilities, libraries, and frameworks. These dependencies are an integral part of your code and any bugs or vulnerabilities in them may affect your code. It's important to review and maintain these dependencies.
|
||||
|
||||
Граф зависимостей предоставляет отличный способ визуализации и изучения зависимостей для репозитория. Дополнительные сведения см. в разделах [Сведения о графе зависимостей](/code-security/supply-chain-security/about-the-dependency-graph) и [Изучение зависимостей репозитория](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository).
|
||||
The dependency graph provides a great way to visualize and explore the dependencies for a repository. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)."
|
||||
|
||||
Также можно настроить репозиторий, чтобы {% data variables.product.company_short %} автоматически оповещал вас всякий раз при обнаружении уязвимости безопасности в одной из зависимостей. Дополнительные сведения см. в статье "[Сведения о {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)".
|
||||
You can also set up your repository so that {% data variables.product.company_short %} alerts you automatically whenever a security vulnerability is found in one of your dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
@@ -1 +1,9 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
|
||||
---
|
||||
ms.openlocfilehash: 484a4230527deebe6f4aeb24ceabdf95eb75b492
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: "148191333"
|
||||
---
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} не может создать вилку репозиториев за пределами предприятия. {% data variables.enterprise.prodname_managed_users_caps %} может разветвить частные или внутренние репозитории, принадлежащие организациям на предприятии, в пространство имен учетной записи пользователя или другие организации, принадлежащие предприятию, в соответствии с политикой предприятия.
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: eb538c8746bf9d5ec4cd0e422e50ccc032309812
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: MT
|
||||
ms.contentlocale: ru-RU
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: "148191372"
|
||||
---
|
||||
Вилка — это новый репозиторий, который совместно использует параметры кода и видимости с исходным "вышестоящим" репозиторием. Вилки часто используются для итерации идей или изменений, прежде чем они будут предложены обратно в вышестоящий репозиторий, например в проектах открытый код или когда у пользователя нет доступа на запись в вышестоящий репозиторий.
|
||||
Reference in New Issue
Block a user