1
0
mirror of synced 2025-12-30 03:01:36 -05:00

Merge branch 'main' into main

This commit is contained in:
Ramya Parimi
2022-03-22 06:25:46 -05:00
committed by GitHub
259 changed files with 2790 additions and 1317 deletions

6
.github/CODEOWNERS vendored
View File

@@ -24,7 +24,7 @@ package.json @github/docs-engineering
/translations/log/ @github/docs-localization @Octomerger
# Site Policy
/content/github/site-policy/ @github/site-policy-admins
/content/site-policy/ @github/site-policy-admins
# Content strategy
/contributing/content-markup-reference.md @github/docs-content-strategy
@@ -32,7 +32,3 @@ package.json @github/docs-engineering
/contributing/content-model.md @github/docs-content-strategy
/contributing/content-style-guide.md @github/docs-content-strategy
/contributing/content-templates.md @github/docs-content-strategy
# Make sure that Octokit maintainers get notified about changes
# relevant to the Octokit libraries (https://github.com/octokit)
/content/rest/reference @github/octokit-maintainers

View File

@@ -23,6 +23,10 @@ jobs:
uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579
with:
ref: ${{ github.head_ref }}
# Need to specify a PAT here because otherwise GITHUB_TOKEN is used
# by default. Workflows won't trigger in that case because actions
# performed with GITHUB_TOKEN don't trigger other workflows.
token: ${{ secrets.DOCUBOT_REPO_PAT }}
- name: Check out base ref
run: git fetch --no-tags --depth=1 origin $GITHUB_BASE_REF

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

View File

@@ -40,9 +40,23 @@ You can also find a list of your recently visited repositories, teams, and proje
## Staying updated with activity from the community
In the "All activity" section of your news feed, you can view updates from repositories you're subscribed to and people you follow. The "All activity" section shows updates from repositories you watch or have starred, and from users you follow.
{% if for-you-feed %}
The main section of your dashboard has two activity feeds:
- Following: Activity by people you follow and from repositories you watch.
- For you: Activity and recommendations based on your {% data variables.product.product_name %} network.
### Following feed
This feed shows activity from repositories and users you have shown a direct interest in, by following a user or watching a repository. For example, you'll see updates when a user you follow:
{% else %}
In the "All activity" section of your news feed, you can view updates from repositories you watch and users you follow.
You'll see updates in your news feed when a user you follow:
{% endif %}
- Stars a repository.
- Follows another user.{% ifversion fpt or ghes or ghec %}
- Creates a public repository.{% endif %}
@@ -51,7 +65,26 @@ You'll see updates in your news feed when a user you follow:
- Forks a public repository.{% endif %}
- Publishes a new release.
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)."
For more information about starring repositories and following people, see "[Following people](/articles/following-people)" and "[Be social](/get-started/quickstart/be-social)."
{% if for-you-feed %}
### For you feed
{% note %}
**Note:** This new tab is currently in public beta and subject to change.
{% endnote %}
This feed shows activity and recommendations based on your network on {% data variables.product.product_name %}. It's designed to provide updates that inspire you, keep you up-to-date, and help you find new communities you want to participate in. Your network includes:
- Repositories you have starred
- Repositories you've contributed to
- Users you follow or sponsor
- Users you've collaborated with
- Organizations you follow
{% endif %}
## Exploring recommended repositories

View File

@@ -14,7 +14,6 @@ shortTitle: Manage access to runners
{% data reusables.actions.enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
{% data reusables.actions.restrict-runner-workflow-beta %}
## About self-hosted runner groups

View File

@@ -256,6 +256,12 @@ By default, {% data variables.product.prodname_dependabot %} attempts to detect
Supported options
{% note %}
**Note:** The `prefix` and the `prefix-development` options have a 15 character limit.
{% endnote %}
- `prefix` specifies a prefix for all commit messages.
- `prefix-development` specifies a separate prefix for all commit messages that update dependencies in the Development dependency group. When you specify a value for this option, the `prefix` is used only for updates to dependencies in the Production dependency group. This is supported by: `bundler`, `composer`, `mix`, `maven`, `npm`, and `pip`.
- `include: "scope"` specifies that any prefix is followed by a list of the dependencies updated in the commit.

View File

@@ -24,7 +24,7 @@ If there's a particular topic that interests you, visit `github.com/topics/<topi
If you've been active on {% data variables.product.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe).
Keep up with recent activity from repositories you watch and people you follow in the "All activity" section of your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
Keep up with recent activity from repositories you watch and people{% if for-you-feed %}, and organizations{% endif %} you follow with your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
{% data reusables.support.ask-and-answer-forum %}

View File

@@ -0,0 +1,50 @@
---
title: Following organizations
intro: 'You can follow organizations on {% data variables.product.product_name %} to receive notifications about their activity.'
versions:
feature: for-you-feed
topics:
- Profile
---
{% note %}
**Note:** The ability to follow organizations is currently in public beta and subject to change.
{% endnote %}
## About followers on {% data variables.product.product_name %}
When you follow organizations, you'll see their public activity on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)."
You can unfollow an organization if you do not wish to see their public activity on {% data variables.product.product_name %}.
## Following an organization on {% data variables.product.product_name %}
1. Go to the organization page you want to follow
2. Click **Follow** in the top-right corner of the header
![Screenshot of the organization header, with the follow button highlighted](/assets/images/help/profile/organization-profile-following.png)
## Unfollowing an organization on {% data variables.product.product_name %}
1. Go to the organization page you want to unfollow
2. Click **Unfollow** in the top-right corner of the header.
![Screenshot of the organization header, with the unfollow button highlighted](/assets/images/help/profile/organization-profile-unfollowing.png)
## Viewing people and organizations a user follows on {% data variables.product.product_name %}
1. Click a user image to display that user's profile.
![User image](/assets/images/help/profile/user-profile-image.png)
2. Click **following** under their profile image.
![User following](/assets/images/help/profile/user-profile-following.png)
{% ifversion fpt or ghec %}
## Further reading
- "[Following people](/get-started/exploring-projects-on-github/following-people)"
{% endif %}

View File

@@ -17,7 +17,7 @@ topics:
## About followers on {% data variables.product.product_name %}
When you follow people, you'll see their public activity in the activity view of your news feed.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you in the discovery view of your news feed.{% endif %}
When you follow people, you'll see their public activity on your personal dashboard.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you.{% endif %} For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)."
You can unfollow someone if you do not wish to see their public activity on {% data variables.product.product_name %}.

View File

@@ -18,6 +18,7 @@ children:
- /finding-ways-to-contribute-to-open-source-on-github
- /saving-repositories-with-stars
- /following-people
- /following-organizations
shortTitle: Explore projects
---

View File

@@ -25,7 +25,7 @@ You can search, sort, and filter your starred repositories and topics on your {%
Starring makes it easy to find a repository or topic again later. You can see all the repositories and topics you have starred by going to your {% data variables.explore.your_stars_page %}.
{% ifversion fpt or ghec %}
You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content in the discovery view of your news feed. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)".
You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content on your personal dashboard. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" and "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)."
{% endif %}
Starring a repository also shows appreciation to the repository maintainer for their work. Many of {% data variables.product.prodname_dotcom %}'s repository rankings depend on the number of stars a repository has. In addition, [Explore](https://github.com/explore) shows popular repositories based on the number of stars they have.

View File

@@ -36,11 +36,11 @@ If you plan to rename a repository that has a {% data variables.product.prodname
{% endif %}
{% tip %}
{% note %}
**Tip:** {% data reusables.organizations.owners-and-admins-can %} rename a repository. {% data reusables.organizations.new-repo-permissions-more-info %}
**Note:** {% data variables.product.prodname_dotcom %} will not redirect calls to an action hosted by a renamed repository. Any workflow that uses that action will fail with the error `repository not found`. Instead, create a new repository and action with the new name and archive the old repository. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
{% endtip %}
{% endnote %}
{% warning %}

View File

@@ -37,7 +37,7 @@ Each CODEOWNERS file assigns the code owners for a single branch in the reposito
For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`.
{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %}
{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4675 %}
## CODEOWNERS file size
CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request.

View File

@@ -7,7 +7,7 @@ versions:
fpt: '*'
ghec: '*'
ghes: '>3.2'
ghae-issue-4974: '*'
ghae: 'issue-4974'
topics:
- Repositories
---

View File

@@ -98,7 +98,7 @@ The Service's bandwidth limitations vary based on the features you use. If we de
While we understand that you may want to promote your Content by posting supporters' names or logos in your Account, the primary focus of the Content posted in or through your Account to the Service should not be advertising or promotional marketing. This includes Content posted in or through Pages, Packages, repositories, and all other parts of the Service. You may include static images, links, and promotional text in the README documents or project description sections associated with your Account, but they must be related to the project you are hosting on GitHub. You may not advertise in other Users' Accounts, such as by posting monetized or excessive bulk content in issues.
You may not promote or distribute content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service/)or [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies/), including excessive automated bulk activity (for example, spamming), get-rich-quick schemes, and misrepresentation or deception related to your promotion.
You may not promote or distribute content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service/) or [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies/), including excessive automated bulk activity (for example, spamming), get-rich-quick schemes, and misrepresentation or deception related to your promotion.
If you decide to post any promotional materials in your Account, you are solely responsible for complying with all applicable laws and regulations, including without limitation the U.S. Federal Trade Commission's Guidelines on Endorsements and Testimonials. We reserve the right to remove any promotional materials or advertisements that, in our sole discretion, violate any GitHub terms or policies.

View File

@@ -0,0 +1,5 @@
# Issues 4834 and 5722
# New feed for personal dashboards and option to follow organizations
versions:
fpt: '*'
ghec: '*'

View File

@@ -76,6 +76,7 @@ sections:
- The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than {% data variables.product.prodname_actions %}. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
- '{% data variables.product.prodname_actions %} now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.'
- Check annotations older than four months will be archived.
- Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18]
- heading: Security Changes
notes:

View File

@@ -1,7 +0,0 @@
{% if restrict-groups-to-workflows %}
{% note %}
**Note:** Configuring the workflows that can access a runner group is currently in beta and subject to change.
{% endnote %}
{% endif %}

View File

@@ -1,4 +1,8 @@
{% ifversion ghae %}
{% ifversion ghae-issue-5752 %}
<!-- Remove this reusable and all references for GA release -->
{% elsif ghae %}
{% note %}

View File

@@ -1,4 +1,9 @@
{% ifversion ghae %}
{% ifversion ghae-issue-5752 %}
<!-- Remove this reusable and all references for GA release -->
{% elsif ghae %}
{% note %}
**Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned repositories is currently in beta and subject to change.

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:ff0c9edba0a40aa9c746a319a6dc8f3299e134f666177dfa4342f4a9910b4b20
size 659833
oid sha256:c7ebcbefd93d8a2a0fa172a36835cfa979ec869b287e22cc0fef1a648a1053d6
size 660091

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:fb1c0e71459563b832c0f0f8a4f860c0c9cf14139c4a7217f8138fd4d473a990
size 1338146
oid sha256:cedb646594b35c17dbb14c93c1d0c35d1af191276a72f482bd4e23513f1c1e03
size 1338039

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:f3c33c3eb6cb2c5a4a44176435637decf31ec38db7eae5338acff0638190a2bc
size 881318
oid sha256:b15fc2d5e8fb601847a784fb57851ae894a53a2fa7804dfe147cacfb0b49dce6
size 881394

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:387a312051b8f97cba29386cdd20480b325f4ead2bbddbf2b181d776e7c00ac9
size 3385989
oid sha256:2c4086ed9a5099499162f8df73a0b34342872660115b381de0046e902c237e5a
size 3387617

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:608e9731086822e5fb454c66182b739b4f20d3a8bea69488851fa6b5e70b9fb4
size 609376
oid sha256:5bbae6e18ddd5745c36dc61cf32eca8e3e14584c0a77f64c89590b6d10b056c1
size 608773

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:a7a35b7e842eec9acd6cb9ebcda4e9ddd034704bba49f4f8971523ff31e9a9af
size 2567986
oid sha256:fc49e2bd15b8b0c96849f5a717cc5dd5e538fc784d1bbba72137b353583e0722
size 2567282

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:ede763d4f0bf7c5cf89d6fc9d52c520c27c6cc58e030fdb22e06185bc34b86db
size 673659
oid sha256:32e78f439b189631db26b41ba879db32e571b2f26b1740b7018fba8e883d9938
size 674054

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:129c5e67cd3396fa2a031cd0da721f4b648741baf2405bdf36af4b15cee32b18
size 3573898
oid sha256:328f624fde4c2f47135a6f38743c16b5c619b1115654a2d520c5e8c14eb6c097
size 3573997

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2b5e686d992c66adbc2fab0e932fc4326929f74e75f98dacbf2c117c1790c6e3
size 598782
oid sha256:3db85e6b024445b7d525a9a32d2bab8f0119852527e6207728775bafa8b3d610
size 600049

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:ba41b694feb8728f96e2c642ba43f4a02aa9f5e41a6cbc05ad475827afc9cd01
size 2447574
oid sha256:f96d21dd420753b813762c2667e5c48adb34ed20d91e779f0399796e267cf684
size 2447784

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:dff4a49d8bacff2bc137fc2154e1e84a50a7de6f8f01d8c78ed67f0b322573bc
size 676895
oid sha256:7690f3082a73b79251d6cd07fd470c7306dd513f5c079e3caec1bac21b7f6ea4
size 677088

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:68dea3ca72e413e961d681afd4757a26f5ee0b655fccc75bee6683b735282394
size 1368047
oid sha256:36b2de51db56aa775837c71e2ec09b37edb3d475d561dc26976a1997b19dacb0
size 1368075

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:610fab4aba6d0b9c98d8173b9f5e88e3d802eaa5bd43e4a3a05b394c661f5b30
size 910047
oid sha256:23a0f769a5b0982fb8de5a3ba4a7459651aa1d0ebfc23311ec1efb3af06e8b97
size 910216

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:edf33e468746f8bd45499d172890ecf6c6e182f24aa102ba0892addd2d6d6380
size 3503719
oid sha256:0b544bebf6c78d3bfcf3889cd9cec72aa587b8b2a7f6f0c7d43bc76e2c26e899
size 3503828

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:0a77aa5c29c8dcbb1af735a4c869bafb86a5a6bd62e90bab075b3ca086cec4f6
size 625131
oid sha256:55ab34ba5a128ad2569f032da3bd3597ce06ce6c82676757759a2a336886bebf
size 625248

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:3ac0b47fa94d4753c7a3f1386fccabc1f77fb7b0275a7b8fbb494f0324e0f893
size 2636202
oid sha256:7186e9c508312737a491909c608425ce376caa934ac5efc1231c15f49bdccc4b
size 2636233

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:f46ea20fa6047c33289c1424c6758045d1f06570f17ef14d2938ceb46b089939
size 689971
oid sha256:2d9d3dc800c2a5c0c60f67abfe38aec284379186aa52b2a77b3cbaf16f189191
size 690617

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:165d82b212796a1e2a2d5df4cbdb672e3ebe93694b22f4b1c72adc214184957a
size 3664525
oid sha256:0768c302b3c7625da74f9c61f5905f0e8a4e17e9770cfc8f18ddd93681ac8dea
size 3668034

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:84f1896f872fc51d04b2dab0e6e5d4fc0de8f2009ebea7e1c51bddc7f0342e02
size 614693
oid sha256:32a1f411274c6c1f5920bd0bf2f4caef72bae7ce7f649bd538d8910c9638a8d7
size 614495

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:d58c056208af6d3694c42c7c18d52a4204884e7055ba2cd8f64050237278f00f
size 2506649
oid sha256:5c9dc0a0276a8455356a14e1f1caab5a85f4f096bd44298fe51ed914d34dcead
size 2507577

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:dc2d88716d79e2235e10b15a6686685954859e773a528e09be38e9cda26a8d58
size 700103
oid sha256:1ebae1c432164fab2125626c0438b5aff75c7e8d65f632aa7c31ce8f195732d5
size 699371

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:3c468ed53b7252495f02bec2eaa4a004475897a66a1c09357145564d3c134cab
size 1421656
oid sha256:4acf995c65898c409a5cd188f20fa6a294384d91c5f13f3bf05a81d96800aa05
size 1421849

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:d4f63c512b449c588541e2bebf1f556eb5d23c28772d9b2ec26a17e06720e996
size 945173
oid sha256:f58c3b4577f9c8eee42a40fbdecd83ed429efda5dadf8580f438e0b3c9116691
size 944891

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:429b7ecde229d2c04020d8c7e3fe4725a4ead459eabb95ef9e2e975a4f79fcb3
size 3619628
oid sha256:0a10d1eb1bd745fc3572eb724cb12a637add2555662d5b2375374bc3b9c5f8c1
size 3619296

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:6c03f6c7f6a65dde6193ec93231bf088c9641c8d8172cffc1a40444a16834308
size 644205
oid sha256:36ec86b80706dbc058b050dd07e49d17629c848b136a486e0f4838df7174da4e
size 643913

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c0a023f678ad0d413b0967e0fbc2123a7a29fc30267ed5e18bd2da3a9cf3ef43
size 2723709
oid sha256:4c1a7315e1e6cc9bf4a5ab99a685c7c3862b804b46fe4d2d0de3f1fcf565637e
size 2721760

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:bd5f89d09df52de206c52b281b0c486efd5b5674e6d092d919d920b4ae86502d
size 713927
oid sha256:b8e3d64ba350dd9c058dceb4726fc5a782b57cb4975beb68e77abee489ef2916
size 713548

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:af4b2c840334ca9ee053dee394bb97033675ad08d935790e7f9b7bbfe61f8f65
size 3789047
oid sha256:ebdaa2d6702271600ab40b3819c82a7fb4b6b5952753c44f8accd0fbedf59de4
size 3787667

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c77cc9ea44a3ce88f75adfb4b0e462a70f0d0f9618c39d5d9e88fd22e377de34
size 634481
oid sha256:d8483d4979467f772b2b693667eb36ac27e84cbb3faf97138f32ab1b5ab4cfe4
size 634774

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:d06af2d3a363a8dea90a4b0856d418cc2d2f25db815ddae6fee5aec70300f703
size 2591441
oid sha256:68a0f20f2bc00e7fec61b1fd7b616298dbc96ceb742ff8b34ba65d285e0139df
size 2592303

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:e87321fc6811d0ab0c4d7c6e76742319c3b89f3320d4758edd99041be50a4693
size 703568
oid sha256:0e66346dea058636aa000103171795548bd2742ec14ad21a3eb983e141be3436
size 702741

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:e484abf831ace5bcfd5077ada3fd2532037ef56cf8c7dd82f90b7d856206e38a
size 1433916
oid sha256:1d37761149634ca646ec089a747875a1f075f92c738cd8fe476b0c2ccfdec9d1
size 1431502

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:a09b40a0071c4cf66372f9c8e938679242602dd254cc9994118e5082462a4dcf
size 954957
oid sha256:58d05c6f5e488ae6db66abedd0fc23b3d2f31ef2089066542e8b6d4664f27ee9
size 955017

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:eca4bee01dddc9117f8da5e0cdd2cdf8ca442dcd720623baa2fe0f132d7ed10a
size 3656711
oid sha256:9994a95cec0b2687b9730c5bd3d78375750b5476674e36396aa3f0de642a7abb
size 3655956

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:fdf064c160dad6188799d750596cbf069a579fe5cfb63be7f8eb92941dec4e7f
size 647751
oid sha256:c96db6e9c6be7a79fd10eeed16e964555721d630d1f6fa197de28c047ebef70b
size 648883

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c415d96320c7df570b3f9fbc9cfe0c790c473e605d2cae3469528bdbfb05ef9f
size 2740330
oid sha256:d8f51ddc7ca8e456df3a73204936d13daf57587ba8d42e764cbb353f72f62d6b
size 2738801

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:8c1ec0d82010c17fae8a0f7d5661625322bb681785d37a3e41ce9f75a3fb3b29
size 716766
oid sha256:947fa0a52b09b47117851a526f03445118820480b917df77371ee6ebbd7f4e0f
size 716535

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:79c021a9d91e909bf28fd0999e5d13341709339288e72562d929e098ac969f40
size 3808893
oid sha256:a882ccf1869fd4efc7ae1c12899513966ebec736de157b41216cb39e30be37f4
size 3810341

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:0ac0ad8430595d6af58c42535fb4bca94c4094568ec0020898ee49921fc72721
size 638379
oid sha256:2622231476be3959cad42a35af14c2b1c9379420ddf2b2c49c8c8fe17b25130b
size 638108

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:dbd786a796b5e6b66e6804e0a09888dd27f65342ba55b8d05f9a08dc12a74544
size 2603947
oid sha256:018682b1be10372d14b22edace423bb85a9778165fc0b9d44739ac0c90c93d40
size 2603273

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c3d517f33169585250b7beee52f77d9adb7d233f57ee2f4fd87c0fcacc7bc048
size 906271
oid sha256:dc544b549dcf0cb6302524c1ec926301b5097b1458af015c77b171ed5724ebe5
size 907395

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:9d6f7620bbe42386a876e3c4ca994890a506a0e3b6292697286d4430c166ee29
size 1571734
oid sha256:323ebeadfddeee813f824ccedf45ebcd41c971bd5d1dfe6c4ec1e4002c2a1290
size 1571811

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2f3b22e4234d9f43568bd9a35f93f3fdfe95835cd98b5a0541d3730a15f6e274
size 1224998
oid sha256:d9fc9f41fd337566e1c195dc9a8ad08a7caaf3bd7ac0fb995d1a2146b6b9d131
size 1224453

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:b393b09dcc655963ada2502dd32e783d1ab324e7a3e86aa210be53eca4b564ea
size 4416589
oid sha256:26a334563c6e6a26e73f2d154b6959d6e18b61a8233e3ac51bd3b8166acdb8ae
size 4417870

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:09f4115509a1a7fd55ed6b14f0ed9fb37b95a1652d8d656d51c419b9f3ee11d6
size 817647
oid sha256:a060b6cddaa10c75d5259ea5a46eea1ef9fb297f2c5e1b5cd42afb02aff55148
size 819319

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:68f335114bb375ee27cd86bc27a13fd527eedb7783d5a245a6b6c926cf8d841e
size 3273885
oid sha256:08189d7bb2a6765341a51b8c7e56f9386c44ddc6506d07fec85e6d41cdedc789
size 3273901

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:0a930f822118744a5dc6e8527b5fbacac1a457a0d7ebb07b9c9e8974171d8057
size 918214
oid sha256:dc009ecabbb56310a244210e521a468884bcc61243b5cd3120ad0b21a2d7533e
size 919674

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:047e4222775d8abd65d89a65e80935289d92c93f4f8d9424e14cc24c40e3ecd8
size 4662824
oid sha256:c1d24b88f9d01e9100cfd6d5327f7b23262c1221d408ef93aefd5fd867e2fe03
size 4662214

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:469f9e58d726244061ba3a41353d2c3a997937b1b29b17f802d1a6df9db1cfe0
size 806035
oid sha256:e82405d94265218a62b24f96461f7c42ab12c6d4a276380e4b908546f3f8ea88
size 806263

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:7e3061027a390da4bfcc012ef6b93cf462be38208222dd63b1be6693016e50f6
size 3121112
oid sha256:f9bc0c287dc17cdb09db34463b3a90c0345d43e28c1e6022ee4414b1b66f6a7a
size 3120326

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:b3ad79ab0cdf875fe3eab4c52359e06704300761139bca80784b8fad99569e91
size 537759
oid sha256:acb882ba567d3c92c57abc5b3cccfa00972abf2b7950a07c00fe486732544eee
size 538314

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:50b21d0df833195261f324a2abb957dee5c5f358424e435fa85e70f61947fdd0
size 1012611
oid sha256:69076567f195c087309e02db75ece772b5f45cde5c3d088d83cde0f1846fd8d5
size 1012977

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:7ca5b06c1c64a450bc0ae733fe3ee55f2ab8ed50fdd328b0f6790807a1289a45
size 737935
oid sha256:11d05e7936af22563d01ec742d39fc38680e995541f8dd1fb51e71035a1153fd
size 739434

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:7179b371c23578853cc8948c11c832031f1e8de133e3194a9e73a72214e03c4c
size 2789117
oid sha256:583226863f99bd763652f7251c044addda225a3745294b4e63e42c34538ac933
size 2790804

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:9e59b2a9afb4c1d1323cc65f76084c266921679cd34774a252ad5e2ad2c7c9ca
size 496691
oid sha256:9b7b531d089684b1e9e9c1fce2a7662df62d15017768178e7b78ab045a5570c1
size 496694

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:80a98440594318b0529e97107a9ba47532f3fb6a07f7d1b1930d99c2c01a40c9
size 2018469
oid sha256:52ae211d3ba8bf0b240d39f89a5862887a0adc7c4f150e07a31ffb45ead97aab
size 2018759

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:ad77bb2b897c3c93b6cca590749a2aa4a5cb86fa12ef995205c70451b7d3b2be
size 548022
oid sha256:1564b76f7a8dacd010f04ca670c62d4932a64922869d910aa289dbb9c362dd9c
size 548088

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:771fdd7285cb93a223ef4b2e08c722bbb29e9ef78efcc60c79bd5ef29cb89f4e
size 2783872
oid sha256:4e9cc5d76be8526f162d2651309936a647b6dc6ac8c62db092b8ef3166013664
size 2781451

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:704990ffeea9abaf7d7b3e1729e8a2961fd6362ecc72bc67d4c47a5de1387dde
size 487985
oid sha256:66e2400fed52f4faa08aeedeaede7db696a7027f787abf302abd90b175decd5d
size 488463

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:b8200466d52d5e8f61cbf712c46d8f8c001a8f8a09ba2a3d0bdb70cd0cbaa37a
size 1896954
oid sha256:cb87dc3b6f149602b5496c7d583adbcb92cc92616a5d95db8445a58b4d33f98e
size 1897002

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:1bfb279bc778e2e614d9dc1d3a5b0b06ddba0eee34cfdb120e172cfbe39ed158
size 837995
oid sha256:e720545c594288b2d42f23c84055e91b91e2baa4888c8e1b071ec82adee186b4
size 838775

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:b2db7c4687e9a43b75e7422f47769a4a12f055300ea7e3841258008170dbee69
size 1635377
oid sha256:7fc2e3eb79ff18806254844a14f91d3d836bd6599d2ae29c4de3e549915f33ee
size 1634448

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:a6a7d034e0f48caee97e1fba8502adf49147bcddcec0d7e14c2264b9cc4d8bc1
size 1105228
oid sha256:745b556987142abccaadfd137938ef68efa27aca8f407187c1307dcb867eb2dc
size 1105003

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:5ad4a6feb5233f01764880315c4ce6705c0c0cf7ae0211907ffcf1f1f8bf614b
size 4207635
oid sha256:d5a24fa318425dc79ed01e2560a80689ea29ba222f49509a35a74cdab3187746
size 4206993

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:1f275f3c75ded67755f324cc00996e0953eda2a48dd0e99806d5e69c651d1e61
size 776421
oid sha256:31825cf0d42cb76d194b3d139b9447899864a82615e2d3581ae3216329161186
size 776284

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:4acf4944ab0c36dd9d94b162fb18ca2a4920a62506da4ddac3f71f2abf325595
size 3266771
oid sha256:fc88f781e277234e425fa41497cd8a953b809189990e262375c61efe220f2ff2
size 3266955

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:ea56582b707485106c97b95e2f23d99ff69996a97ca5258b76a5cf8c1bff18b7
size 852908
oid sha256:f994577167e57831a068aba953a3c4253048b060ec1a8cd641ab69914e70566c
size 854392

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:f70cc3fe84262427cc8a5cf949565f6eaae988092db5db56e132e3e269e58226
size 4550464
oid sha256:b81836667a86ccf1a6f082a22dec7f8ae4c5ddbdbf02c4eb7f9a3adacfb7a524
size 4553982

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:5fefb22f038f49bb9e2206b26771bfb74939202e7d2f8fe2ca8962900ef1f841
size 765117
oid sha256:9ae58c209d322d75e81c7efc5068141bd468a5f7f448e12ca0715a95fe59a034
size 765411

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:f97312508215bf8493c399fa264ecd1d053ffdf559fa220f40523df46b0ce203
size 3103523
oid sha256:fa9559d53b55f9c454538799be28addf091f5c09475176b0dd8592fce96323b8
size 3104241

58
package-lock.json generated
View File

@@ -11,7 +11,7 @@
"@primer/css": "^19.4.0",
"@primer/octicons": "17.0.0",
"@primer/octicons-react": "17.0.0",
"@primer/react": "^34.6.0",
"@primer/react": "^34.7.1",
"@react-aria/ssr": "^3.1.0",
"accept-language-parser": "^1.5.0",
"ajv": "^8.9.0",
@@ -3603,9 +3603,9 @@
"integrity": "sha512-+Gwo89YK1OFi6oubTlah/zPxxzMNaMLy+inECAYI646KIFdzzhAsKWb3z5tSOu5Ff7no4isRV64rWfMSKLZclw=="
},
"node_modules/@primer/react": {
"version": "34.6.0",
"resolved": "https://registry.npmjs.org/@primer/react/-/react-34.6.0.tgz",
"integrity": "sha512-a0Mh6YmpEyQF6ad0mnfOJoC+y1heDM4uuvBcQQKJQ28DVeif5mn+slCD2C9ZQvnhkl4qnh3iqXOTxmKN5fCHNQ==",
"version": "34.7.1",
"resolved": "https://registry.npmjs.org/@primer/react/-/react-34.7.1.tgz",
"integrity": "sha512-9OLRo3N1/B/jqb7aJPY7xmtyKM8afZlmWLnEOmT8LOCmuwPiRXI+4GsJjaV9RPx3h8rUXBQwpaYZGDDj9+/OjA==",
"dependencies": {
"@primer/behaviors": "1.1.0",
"@primer/octicons-react": "16.1.1",
@@ -4772,6 +4772,17 @@
"string-width": "^4.1.0"
}
},
"node_modules/ansi-colors": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/ansi-colors/-/ansi-colors-4.1.1.tgz",
"integrity": "sha512-JoX0apGbHaUJBNl6yF+p6JAFYZ666/hhCGKN5t9QFjbJQKUU/g8MNbFDbvfrgKXvI1QpZplPOnwIo99lX/AAmA==",
"dev": true,
"optional": true,
"peer": true,
"engines": {
"node": ">=6"
}
},
"node_modules/ansi-escapes": {
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-4.3.2.tgz",
@@ -8214,6 +8225,20 @@
"node": ">=10.13.0"
}
},
"node_modules/enquirer": {
"version": "2.3.6",
"resolved": "https://registry.npmjs.org/enquirer/-/enquirer-2.3.6.tgz",
"integrity": "sha512-yjNnPr315/FjS4zIsUxYguYUPP2e1NK4d7E7ZOLiyYCcbFBiTMyID+2wvm2w6+pZ/odMA7cRkjhsPbltwBOrLg==",
"dev": true,
"optional": true,
"peer": true,
"dependencies": {
"ansi-colors": "^4.1.1"
},
"engines": {
"node": ">=8.6"
}
},
"node_modules/ensure-posix-path": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/ensure-posix-path/-/ensure-posix-path-1.1.1.tgz",
@@ -25157,9 +25182,9 @@
"integrity": "sha512-+Gwo89YK1OFi6oubTlah/zPxxzMNaMLy+inECAYI646KIFdzzhAsKWb3z5tSOu5Ff7no4isRV64rWfMSKLZclw=="
},
"@primer/react": {
"version": "34.6.0",
"resolved": "https://registry.npmjs.org/@primer/react/-/react-34.6.0.tgz",
"integrity": "sha512-a0Mh6YmpEyQF6ad0mnfOJoC+y1heDM4uuvBcQQKJQ28DVeif5mn+slCD2C9ZQvnhkl4qnh3iqXOTxmKN5fCHNQ==",
"version": "34.7.1",
"resolved": "https://registry.npmjs.org/@primer/react/-/react-34.7.1.tgz",
"integrity": "sha512-9OLRo3N1/B/jqb7aJPY7xmtyKM8afZlmWLnEOmT8LOCmuwPiRXI+4GsJjaV9RPx3h8rUXBQwpaYZGDDj9+/OjA==",
"requires": {
"@primer/behaviors": "1.1.0",
"@primer/octicons-react": "16.1.1",
@@ -26158,6 +26183,14 @@
"string-width": "^4.1.0"
}
},
"ansi-colors": {
"version": "4.1.1",
"resolved": "https://registry.npmjs.org/ansi-colors/-/ansi-colors-4.1.1.tgz",
"integrity": "sha512-JoX0apGbHaUJBNl6yF+p6JAFYZ666/hhCGKN5t9QFjbJQKUU/g8MNbFDbvfrgKXvI1QpZplPOnwIo99lX/AAmA==",
"dev": true,
"optional": true,
"peer": true
},
"ansi-escapes": {
"version": "4.3.2",
"resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-4.3.2.tgz",
@@ -28960,6 +28993,17 @@
"tapable": "^2.2.0"
}
},
"enquirer": {
"version": "2.3.6",
"resolved": "https://registry.npmjs.org/enquirer/-/enquirer-2.3.6.tgz",
"integrity": "sha512-yjNnPr315/FjS4zIsUxYguYUPP2e1NK4d7E7ZOLiyYCcbFBiTMyID+2wvm2w6+pZ/odMA7cRkjhsPbltwBOrLg==",
"dev": true,
"optional": true,
"peer": true,
"requires": {
"ansi-colors": "^4.1.1"
}
},
"ensure-posix-path": {
"version": "1.1.1",
"resolved": "https://registry.npmjs.org/ensure-posix-path/-/ensure-posix-path-1.1.1.tgz",

View File

@@ -11,9 +11,9 @@
"dependencies": {
"@github/failbot": "0.8.0",
"@primer/css": "^19.4.0",
"@primer/react": "^34.7.1",
"@primer/octicons": "17.0.0",
"@primer/octicons-react": "17.0.0",
"@primer/react": "^34.6.0",
"@react-aria/ssr": "^3.1.0",
"accept-language-parser": "^1.5.0",
"ajv": "^8.9.0",

View File

@@ -2,7 +2,7 @@ import React, { useEffect } from 'react'
import App from 'next/app'
import type { AppProps, AppContext } from 'next/app'
import Head from 'next/head'
import { useTheme, ThemeProvider } from '@primer/react'
import { ThemeProvider, ThemeProviderProps } from '@primer/react'
import { SSRProvider } from '@react-aria/ssr'
import { defaultComponentThemeProps, getThemeProps } from 'components/lib/getThemeProps'
@@ -14,7 +14,7 @@ import { LanguagesContext, LanguagesContextT } from 'components/context/Language
type MyAppProps = AppProps & {
csrfToken: string
themeProps: typeof defaultComponentThemeProps
themeProps: typeof defaultComponentThemeProps & Pick<ThemeProviderProps, 'colorMode'>
languagesContext: LanguagesContextT
}
const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext }: MyAppProps) => {
@@ -51,9 +51,13 @@ const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext }
<meta name="csrf-token" content={csrfToken} />
</Head>
<SSRProvider>
<ThemeProvider dayScheme={themeProps.dayTheme} nightScheme={themeProps.nightTheme}>
<ThemeProvider
colorMode={themeProps.colorMode}
dayScheme={themeProps.dayTheme}
nightScheme={themeProps.nightTheme}
preventSSRMismatch
>
<LanguagesContext.Provider value={languagesContext}>
<SetTheme themeProps={themeProps} />
<Component {...pageProps} />
</LanguagesContext.Provider>
</ThemeProvider>
@@ -76,15 +80,4 @@ MyApp.getInitialProps = async (appContext: AppContext) => {
}
}
const SetTheme = ({ themeProps }: { themeProps: typeof defaultComponentThemeProps }) => {
// Cause primer/components to re-evaluate the 'auto' color mode on client side render
const { setColorMode } = useTheme()
useEffect(() => {
setTimeout(() => {
setColorMode(themeProps.colorMode as any)
})
}, [])
return null
}
export default MyApp

View File

@@ -2,6 +2,7 @@
title: Comandos de flujo de trabajo para Acciones de GitHub
shortTitle: Comandos de flujo de trabajo
intro: Puedes usar comandos de flujo de trabajo cuando ejecutas comandos de Shell en un flujo de trabajo o en el código de una acción.
defaultTool: bash
redirect_from:
- /articles/development-tools-for-github-actions
- /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions
@@ -26,10 +27,24 @@ Las acciones pueden comunicarse con la máquina del ejecutor para establecer var
La mayoría de los comandos de los flujos de trabajo utilizan el comando `echo` en un formato específico, mientras que otras se invocan si escribes a un archivo. Para obtener más información, consulta la sección ["Archivos de ambiente".](#environment-files)
``` bash
### Ejemplo
{% bash %}
```bash{:copy}
echo ":: Workflow-Command Parameter1 ={data}, parameter2 ={data}::{command value}"
```
{% endbash %}
{% powershell %}
```pwsh{:copy}
Write-Output "::workflow-command parameter1={data},parameter2={data}::{command value}"
```
{% endpowershell %}
{% note %}
**Nota:** los nombres de comandos y parámetros de flujo de trabajo no distinguen mayúsculas de minúsculas.
@@ -46,14 +61,18 @@ echo ":: Workflow-Command Parameter1 ={data}, parameter2 ={data}::{command value
El [actions/toolkit](https://github.com/actions/toolkit) incluye varias funciones que se pueden ejecutar como comandos de flujo de trabajo. Utiliza la sintaxis `::` para ejecutar los comandos de flujo de trabajo dentro de tu archivo YAML; estos comandos se envían entonces a través de `stdout`. Por ejemplo, en vez de utilizar código para configurar una salida, como se muestra aquí:
```javascript
```javascript{:copy}
core.setOutput('SELECTED_COLOR', 'green');
```
### Example: Setting a value
Puedes utilizar el comando `set-output` en tu flujo de trabajo para configurar el mismo valor:
{% bash %}
{% raw %}
``` yaml
```yaml{:copy}
- name: Set selected color
run: echo '::set-output name=SELECTED_COLOR::green'
id: random-color-generator
@@ -62,6 +81,22 @@ Puedes utilizar el comando `set-output` en tu flujo de trabajo para configurar e
```
{% endraw %}
{% endbash %}
{% powershell %}
{% raw %}
```yaml{:copy}
- name: Set selected color
run: Write-Output "::set-output name=SELECTED_COLOR::green"
id: random-color-generator
- name: Get color
run: Write-Output "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}"
```
{% endraw %}
{% endpowershell %}
La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles dentro de un flujo de trabajo:
| Funcion del Toolkit | Comando equivalente del flujo de trabajo |
@@ -86,186 +121,336 @@ La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles
## Configurar un parámetro de salida
```
Establece un parámetro de salida de la acción.
```{:copy}
::set-output name={name}::{value}
```
Establece un parámetro de salida de la acción.
Opcionalmente, también puedes declarar parámetros de salida en el archivo de metadatos de una acción. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)".
### Ejemplo
### Example: Setting an output parameter
``` bash
{% bash %}
```bash{:copy}
echo "::set-output name=action_fruit::strawberry"
```
## Agregar un mensaje de depuración
{% endbash %}
{% powershell %}
```pwsh{:copy}
Write-Output "::set-output name=action_fruit::strawberry"
```
::debug::{message}
```
{% endpowershell %}
## Agregar un mensaje de depuración
Imprime un mensaje de depuración para el registro. Debes crear un archivo `ACTIONS_STEP_DEBUG` designado secretamente con el valor `true` para ver los mensajes de depuración establecidos por este comando en el registro. Para obtener más información, consulta la sección "[Habilitar el registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging)."
### Ejemplo
```{:copy}
::debug::{message}
```
``` bash
### Example: Setting a debug message
{% bash %}
```bash{:copy}
echo "::debug::Set the Octocat variable"
```
{% endbash %}
{% powershell %}
```pwsh{:copy}
Write-Output "::debug::Set the Octocat variable"
```
{% endpowershell %}
{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
## Configurar un mensaje de aviso
```
Crea un mensaje de aviso e imprime el mensaje en la bitácora. {% data reusables.actions.message-annotation-explanation %}
```{:copy}
::notice file={name},line={line},endLine={endLine},title={title}::{message}
```
Crea un mensaje de aviso e imprime el mensaje en la bitácora. {% data reusables.actions.message-annotation-explanation %}
{% data reusables.actions.message-parameters %}
### Ejemplo
### Example: Setting a notice message
``` bash
{% bash %}
```bash{:copy}
echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
```
{% endbash %}
{% powershell %}
```pwsh{:copy}
Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
```
{% endpowershell %}
{% endif %}
## Configurar un mensaje de advertencia
```
Crea un mensaje de advertencia e imprime el mensaje en el registro. {% data reusables.actions.message-annotation-explanation %}
```{:copy}
::warning file={name},line={line},endLine={endLine},title={title}::{message}
```
Crea un mensaje de advertencia e imprime el mensaje en el registro. {% data reusables.actions.message-annotation-explanation %}
{% data reusables.actions.message-parameters %}
### Ejemplo
### Example: Setting a warning message
``` bash
{% bash %}
```bash{:copy}
echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
```
{% endbash %}
{% powershell %}
```pwsh{:copy}
Write-Output "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
```
{% endpowershell %}
## Configurar un mensaje de error
```
Crea un mensaje de error e imprime el mensaje en el registro {% data reusables.actions.message-annotation-explanation %}
```{:copy}
::error file={name},line={line},endLine={endLine},title={title}::{message}
```
Crea un mensaje de error e imprime el mensaje en el registro {% data reusables.actions.message-annotation-explanation %}
{% data reusables.actions.message-parameters %}
### Ejemplo
### Example: Setting an error message
``` bash
{% bash %}
```bash{:copy}
echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
```
{% endbash %}
{% powershell %}
```pwsh{:copy}
Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
```
{% endpowershell %}
## Agrupar líneas de las bitácoras
```
Crea un grupo expansible en la bitácora. Para crear un grupo, utiliza el comando `group` y especifica un `title`. Todo lo que imprimas en la bitácora entre los comandos `group` y `endgroup` se anidará dentro de una entrada expansible en la misma.
```{:copy}
::group::{title}
::endgroup::
```
Crea un grupo expansible en la bitácora. Para crear un grupo, utiliza el comando `group` y especifica un `title`. Todo lo que imprimas en la bitácora entre los comandos `group` y `endgroup` se anidará dentro de una entrada expansible en la misma.
### Example: Grouping log lines
### Ejemplo
{% bash %}
```bash
echo "::group::My title"
echo "Inside group"
echo "::endgroup::"
```yaml{:copy}
jobs:
bash-example:
runs-on: ubuntu-latest
steps:
- name: Group of log lines
run: |
echo "::group::My title"
echo "Inside group"
echo "::endgroup::"
```
{% endbash %}
{% powershell %}
```yaml{:copy}
jobs:
powershell-example:
runs-on: windows-latest
steps:
- name: Group of log lines
run: |
Write-Output "::group::My title"
Write-Output "Inside group"
Write-Output "::endgroup::"
```
{% endpowershell %}
![Grupo plegable en la bitácora de una ejecución de flujo de trabajo](/assets/images/actions-log-group.png)
## Enmascarar un valor en el registro
```
```{:copy}
::add-mask::{value}
```
El enmascaramiento de un valor impide que una cadena o variable se imprima en el registro. Cada palabra enmascarada separada por un espacio en blanco se reemplaza con el carácter `*`. Puedes usar una variable de entorno o cadena para el `valor` de la máscara.
### Ejemplo de enmascaramiento de una cadena
### Example: Masking a string
Cuando imprimas `"Mona The Octocat"` en el registro, verás `"***"`.
```bash
{% bash %}
```bash{:copy}
echo "::add-mask::Mona The Octocat"
```
### Ejemplo de enmascaramiento de una variable de entorno
{% endbash %}
{% powershell %}
```pwsh{:copy}
Write-Output "::add-mask::Mona The Octocat"
```
{% endpowershell %}
### Example: Masking an environment variable
Cuando imprimes la variable `MY_NAME` o el valor `"Mona The Octocat"` en el registro, verás `"***"` en lugar de `"Mona The Octocat"`.
```bash
MY_NAME="Mona The Octocat"
echo "::add-mask::$MY_NAME"
{% bash %}
```yaml{:copy}
jobs:
bash-example:
runs-on: ubuntu-latest
env:
MY_NAME: "Mona The Octocat"
steps:
- name: bash-version
run: echo "::add-mask::$MY_NAME"
```
{% endbash %}
{% powershell %}
```yaml{:copy}
jobs:
powershell-example:
runs-on: windows-latest
env:
MY_NAME: "Mona The Octocat"
steps:
- name: powershell-version
run: Write-Output "::add-mask::$env:MY_NAME"
```
{% endpowershell %}
## Detener e iniciar comandos de flujo de trabajo
`::stop-commands::{endtoken}`
Deja de procesar cualquier comando de flujo de trabajo. Este comando especial te permite registrar lo que sea sin ejecutar accidentalmente un comando de flujo de trabajo. Por ejemplo, podrías dejar de registrar para producir un script completo que tenga comentarios.
```{:copy}
::stop-commands::{endtoken}
```
Para parar el procesamiento de los comandos de flujo de trabajo, pasa un token único a `stop-commands`. Para resumir los comandos de flujo de trabajo de procesamiento, pasa el mismo token que utilizaste para detener los comandos de flujo de trabajo.
{% warning %}
**Advertencia:** Asegúrate de que el token que estás utilizando se genere aleatoriamente y sea único para cada ejecución. Tal como se demuestra en el siguiente ejemplo, puedes generar un hash único de tu `github.token` para cada ejecución.
**Advertencia:** Asegúrate de que el token que estás utilizando se genere aleatoriamente y sea único para cada ejecución.
{% endwarning %}
```
```{:copy}
::{endtoken}::
```
### Ejemplo deteniendo e iniciando los comandos de un flujo de trabajo
### Example: Stopping and starting workflow commands
{% bash %}
{% raw %}
```yaml
```yaml{:copy}
jobs:
workflow-command-job:
runs-on: ubuntu-latest
steps:
- name: disable workflow commands
- name: Disable workflow commands
run: |
echo '::warning:: this is a warning'
echo "::stop-commands::`echo -n ${{ github.token }} | sha256sum | head -c 64`"
echo '::warning:: this will NOT be a warning'
echo "::`echo -n ${{ github.token }} | sha256sum | head -c 64`::"
echo '::warning:: this is a warning again'
echo '::warning:: This is a warning message, to demonstrate that commands are being processed.'
stopMarker=$(uuidgen)
echo "::stop-commands::$stopMarker"
echo '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.'
echo "::$stopMarker::"
echo '::warning:: This is a warning again, because stop-commands has been turned off.'
```
{% endraw %}
{% endbash %}
{% powershell %}
{% raw %}
```yaml{:copy}
jobs:
workflow-command-job:
runs-on: windows-latest
steps:
- name: Disable workflow commands
run: |
Write-Output '::warning:: This is a warning message, to demonstrate that commands are being processed.'
$stopMarker = New-Guid
Write-Output "::stop-commands::$stopMarker"
Write-Output '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.'
Write-Output "::$stopMarker::"
Write-Output '::warning:: This is a warning again, because stop-commands has been turned off.'
```
{% endraw %}
{% endpowershell %}
## Hacer eco en las salidas de comando
```
Habilita o inhabilita el hacer eco en los comandos de los flujos de trabajo. Por ejemplo, si utilizas el comando `set-output` en un flujo de trabajo, este configura un parámetro de salida pero la bitácora de la ejecución del flujo de trabajo no muestra al comando mismo. Si habilitas el eco del comando, entonces la bitácora lo mostrará, tal como en `::set-output name={name}::{value}`.
```{:copy}
::echo::on
::echo::off
```
Habilita o inhabilita el hacer eco en los comandos de los flujos de trabajo. Por ejemplo, si utilizas el comando `set-output` en un flujo de trabajo, este configura un parámetro de salida pero la bitácora de la ejecución del flujo de trabajo no muestra al comando mismo. Si habilitas el eco del comando, entonces la bitácora lo mostrará, tal como en `::set-output name={name}::{value}`.
El eco de comando se encuentra inhabilitado predeterminadamente. Sin embargo, los comandos de flujo de trabajo hacen eco si existen errores para procesarlos.
Los comandos `add-mask`, `debug`, `warning` y `error` no son compatibles con el eco porque sus salidas ya hicieron eco en la bitácora.
También puedes habilitar el eco de comandos globalmente si activas la generación de bitácoras de depuración de pasos utilizando el secreto `ACTIONS_STEP_DEBUG`. Para obtener más información, consulta la sección "[Habilitar el registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging)". Como contraste, el comando de flujo de trabajo `echo` te permite habilitar el eco de comandos en un nivel más granular en vez de habilitarlo para cada flujo de trabajo en un repositorio.
### Ejemplo de cómo alternar el eco de comandos
### Example: Toggling command echoing
```yaml
{% bash %}
```yaml{:copy}
jobs:
workflow-command-job:
runs-on: ubuntu-latest
@@ -279,9 +464,29 @@ jobs:
echo '::set-output name=action_echo::disabled'
```
El paso anterior imprime las siguientes líneas en la bitácora:
{% endbash %}
{% powershell %}
```yaml{:copy}
jobs:
workflow-command-job:
runs-on: windows-latest
steps:
- name: toggle workflow command echoing
run: |
write-output "::set-output name=action_echo::disabled"
write-output "::echo::on"
write-output "::set-output name=action_echo::enabled"
write-output "::echo::off"
write-output "::set-output name=action_echo::disabled"
```
{% endpowershell %}
The example above prints the following lines to the log:
```{:copy}
::set-output name=action_echo::enabled
::echo::off
```
@@ -298,13 +503,13 @@ El comando `save-state` solo puede ejecutarse dentro de una acción y no está d
Este ejemplo utiliza JavaScript para ejecutar el comando `save-state`. La variable de ambiente resultante se nombra `STATE_processID` con el valor de `12345`:
``` javascript
```javascript{:copy}
console.log('::save-state name=processID::12345')
```
La variable `STATE_processID` se encontrará entonces exclusivamente disponible para el script de limpieza que se ejecuta bajo la acción `main`. Este ejemplo se ejecuta en `main` y utiliza JavaScript para mostrar el valor asignado a la variable de ambiente `STATE_processID`:
``` javascript
```javascript{:copy}
console.log("The running PID from the main action is: " + process.env.STATE_processID);
```
@@ -312,37 +517,70 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro
Durante la ejecución de un flujo de trabajo, el ejecutor genera archivos temporales que pueden utilizarse para llevar a cabo ciertas acciones. La ruta a estos archivos se expone a través de variables de ambiente. Necesitarás utilizar codificación UTF-8 cuando escribas en estos archivos para garantizar el procesamiento adecuado de los comandos. Se pueden escribir varios comandos en el mismo archivo, separados por líneas nuevas.
{% warning %}
{% powershell %}
**Advertencia:** en Windows, el PowerShell tradicional (`shell: powershell`) no utiliza el cifrado UTF-8 predeterminado.
{% note %}
When using `shell: powershell`, you must specify UTF-8 encoding. Por ejemplo:
**Note:** PowerShell versions 5.1 and below (`shell: powershell`) do not use UTF-8 by default, so you must specify the UTF-8 encoding. Por ejemplo:
```yaml
```yaml{:copy}
jobs:
legacy-powershell-example:
uses: windows-2019
runs-on: windows-latest
steps:
- shell: powershell
run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
run: |
"mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
```
Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8.
PowerShell Core versions 6 and higher (`shell: pwsh`) use UTF-8 by default. Por ejemplo:
{% endwarning %}
```yaml{:copy}
jobs:
powershell-core-example:
runs-on: windows-latest
steps:
- shell: pwsh
run: |
"mypath" >> $env:GITHUB_PATH
```
{% endnote %}
{% endpowershell %}
## Configurar una variable de ambiente
``` bash
{% bash %}
```bash{:copy}
echo "{environment_variable_name}={value}" >> $GITHUB_ENV
```
{% endbash %}
{% powershell %}
- Using PowerShell version 6 and higher:
```pwsh{:copy}
"{environment_variable_name}={value}" >> $env:GITHUB_ENV
```
- Using PowerShell version 5.1 and below:
```powershell{:copy}
"{environment_variable_name}={value}" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
```
{% endpowershell %}
You can make an environment variable available to any subsequent steps in a workflow job by defining or updating the environment variable and writing this to the `GITHUB_ENV` environment file. El paso que crea o actualiza la variable de ambiente no tiene acceso al valor nuevo, pero todos los pasos subsecuentes en un job tendrán acceso. The names of environment variables are case-sensitive, and you can include punctuation. Para obtener más información, consulta "[Variables del entorno](/actions/learn-github-actions/environment-variables)".
### Ejemplo
{% bash %}
{% raw %}
```
```yaml{:copy}
steps:
- name: Set the value
id: step_one
@@ -355,11 +593,31 @@ steps:
```
{% endraw %}
{% endbash %}
{% powershell %}
{% raw %}
```yaml{:copy}
steps:
- name: Set the value
id: step_one
run: |
"action_state=yellow" >> $env:GITHUB_ENV
- name: Use the value
id: step_two
run: |
Write-Output "${{ env.action_state }}" # This will output 'yellow'
```
{% endraw %}
{% endpowershell %}
### Secuencias de línea múltiple
Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la siguiente sintaxis.
```
```{:copy}
{name}<<{delimiter}
{value}
{delimiter}
@@ -367,29 +625,75 @@ Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la s
#### Ejemplo
En este ejemplo, utilizamos `EOF` como delimitador y configuramos la variable de ambiente `JSON_RESPONSE` para el valor de la respuesta de curl.
```yaml
This example uses `EOF` as a delimiter, and sets the `JSON_RESPONSE` environment variable to the value of the `curl` response.
{% bash %}
```yaml{:copy}
steps:
- name: Set the value
- name: Set the value in bash
id: step_one
run: |
echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
curl https://httpbin.org/json >> $GITHUB_ENV
curl https://example.lab >> $GITHUB_ENV
echo 'EOF' >> $GITHUB_ENV
```
## Agregar una ruta de sistema
{% endbash %}
``` bash
echo "{path}" >> $GITHUB_PATH
{% powershell %}
```yaml{:copy}
steps:
- name: Set the value in pwsh
id: step_one
run: |
"JSON_RESPONSE<<EOF" >> $env:GITHUB_ENV
(Invoke-WebRequest -Uri "https://example.lab").Content >> $env:GITHUB_ENV
"EOF" >> $env:GITHUB_ENV
shell: pwsh
```
{% endpowershell %}
## Agregar una ruta de sistema
Antepone un directorio a la variable de sistema `PATH` y la hace disponible automáticamente para todas las acciones subsecuentes en el job actual; la acción que se está ejecutando actualmente no puede acceder a la variable de ruta actualizada. Para ver las rutas definidas actualmente para tu job, puedes utilizar `echo "$PATH"` en un paso o en una acción.
{% bash %}
```bash{:copy}
echo "{path}" >> $GITHUB_PATH
```
{% endbash %}
{% powershell %}
```pwsh{:copy}
"{path}" >> $env:GITHUB_PATH
```
{% endpowershell %}
### Ejemplo
Este ejemplo demuestra cómo agregar el directorio `$HOME/.local/bin` del usuario al `PATH`:
``` bash
{% bash %}
```bash{:copy}
echo "$HOME/.local/bin" >> $GITHUB_PATH
```
{% endbash %}
This example demonstrates how to add the user `$env:HOMEPATH/.local/bin` directory to `PATH`:
{% powershell %}
```pwsh{:copy}
"$env:HOMEPATH/.local/bin" >> $env:GITHUB_PATH
```
{% endpowershell %}

View File

@@ -17,7 +17,11 @@ topics:
Si configuras un nombre del host en lugar de una dirección IP codificada de forma rígida, podrás cambiar el hardware físico que ejecuta {% data variables.product.product_location %} sin afectar a los usuarios o al software del cliente.
La configuración del nombre de host en la {% data variables.enterprise.management_console %} debe ajustarse a un nombre de dominio adecuado y que cumpla con todos los requisitos (FQDN) el cual se pueda resolver en la internet o dentro de tu red interna. Por ejemplo, tu configuración de nombre del host podría ser `github.companyname.com.` También recomendamos habilitar el aislamiento de subdominio para el nombre del host elegido a fin de mitigar varias vulnerabilidades del estilo cross-site scripting. Para obtener más información, consulta [Sección 2.1 del HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2).
La configuración del nombre de host en la {% data variables.enterprise.management_console %} debe ajustarse a un nombre de dominio adecuado y que cumpla con todos los requisitos (FQDN) el cual se pueda resolver en la internet o dentro de tu red interna. For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}.
After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)."
For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2).
{% data reusables.enterprise_installation.changing-hostname-not-supported %}
@@ -29,4 +33,4 @@ La configuración del nombre de host en la {% data variables.enterprise.manageme
{% data reusables.enterprise_management_console.test-domain-settings-failure %}
{% data reusables.enterprise_management_console.save-settings %}
Después de configurar un nombre del host, recomendamos que habilites el aislamiento de subdominio para {% data variables.product.product_location %}. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)."
To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)."

View File

@@ -19,25 +19,32 @@ El tiempo requerido para la tolerancia de fallos depende de cuánto le tome para
{% data reusables.enterprise_installation.promoting-a-replica %}
1. Para permitir que la replicación finalice antes de cambiar aparatos, pon el aparato principal en modo mantenimiento:
- Para usar el administrador de consola, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)"
- También puedes usar el comando `ghe-maintenance -s`.
1. If the primary appliance is available, to allow replication to finish before you switch appliances, on the primary appliance, put the primary appliance into maintenance mode.
- Put the appliance into maintenance mode.
- Para usar el administrador de consola, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)"
- También puedes usar el comando `ghe-maintenance -s`.
```shell
$ ghe-maintenance -s
```
- Cuando la cantidad de operaciones activas de Git, consultas de MySQL y jobs de Resque lleguen a cero, espera 30 segundos.
{% note %}
**Nota:** Nomad siempre tendrá jobs en ejecución, incluso si está en modo de mantenimiento, así que puedes ignorar estos jobs de forma segura.
{% endnote %}
- Para verificar que todos los canales de replicación informan `OK`, utiliza el comando `ghe-repl-status -vv`.
```shell
$ ghe-maintenance -s
$ ghe-repl-status -vv
```
2. Cuando la cantidad de operaciones activas de Git, consultas de MySQL y jobs de Resque lleguen a cero, espera 30 segundos.
{% note %}
**Nota:** Nomad siempre tendrá jobs en ejecución, incluso si está en modo de mantenimiento, así que puedes ignorar estos jobs de forma segura.
{% endnote %}
3. Para verificar que todos los canales de replicación informan `OK`, utiliza el comando `ghe-repl-status -vv`.
```shell
$ ghe-repl-status -vv
```
4. Para frenar la replicación e impulsar el aparato de réplica a un estado primario, utiliza el comando `ghe-repl-promote`. Esto también pondrá de forma automática al nodo primario en nodo mantenimiento si es accesible.
4. On the replica appliance, to stop replication and promote the replica appliance to primary status, use the `ghe-repl-promote` command. Esto también pondrá de forma automática al nodo primario en nodo mantenimiento si es accesible.
```shell
$ ghe-repl-promote
```

View File

@@ -25,7 +25,7 @@ Existen tres tipos de migraciones que se pueden realizar:
En una migración, todo gira en torno a un repositorio. La mayoría de los datos asociados con un repositorio se pueden migrar. Por ejemplo, un repositorio dentro de una organización migrará el repositorio *y* la organización, así como los usuarios, equipos, propuestas y solicitudes de extracción asociados con el repositorio.
Los elementos de la tabla a continuación se pueden migrar con un repositorio. Los elementos que no se muestren en la lista de datos migrados no se pueden migrar.
Los elementos de la tabla a continuación se pueden migrar con un repositorio. Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets.
{% data reusables.enterprise_migrations.fork-persistence %}

View File

@@ -25,7 +25,7 @@ shortTitle: Verificar la llave SSH existente
# Lists the files in your .ssh directory, if they exist
```
3. Comprueba la lista de directorio para ver si ya tiene una clave SSH pública. Predeterminadamente, {% ifversion ghae %}el nombre de archivo de una llave pública para {% data variables.product.product_name %} es *id_rsa.pub*.{% elsif fpt or ghes %}los nombres de archivo de las llaves públicas compatibles para {% data variables.product.product_name %} son una de las siguientes.
3. Comprueba la lista de directorio para ver si ya tiene una clave SSH pública. Predeterminadamente, {% ifversion ghae %}el nombre de archivo de una llave pública para {% data variables.product.product_name %} es *id_rsa.pub*.{% else %}los nombres de archivo de las llaves públicas compatibles para {% data variables.product.product_name %} son una de las siguientes.
- *id_rsa.pub*
- *id_ecdsa.pub*
- *id_ed25519.pub*{% endif %}

View File

@@ -33,7 +33,7 @@ Si eso funcionó, ¡fantástico! De lo contrario, puede que debas [seguir nuestr
Si puedes ingresar a `git@ssh.{% data variables.command_line.backticks %}` por SSH a través del puerto 443, podrás reemplazar los parámetros SSH para forzar que cualquier conexión a {% data variables.product.product_location %} se ejecute a través de ese servidor y puerto.
Para configurar esto en tu archivo de configuración SSH, edita el archivo en `~/.ssh/config` y agrega esta sección:
To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
```
Host {% data variables.command_line.codeblock %}

Some files were not shown because too many files have changed in this diff Show More