diff --git a/.all-contributorsrc b/.all-contributorsrc
index 6a608ccc2052..e341d7a9bb7c 100644
--- a/.all-contributorsrc
+++ b/.all-contributorsrc
@@ -285,6 +285,77 @@
"bug",
"code"
]
+ },
+ {
+ "login": "BenJam",
+ "name": "Benjamin Nickolls",
+ "avatar_url": "https://avatars2.githubusercontent.com/u/158833?v=4",
+ "profile": "https://github.com/BenJam",
+ "contributions": [
+ "doc"
+ ]
+ },
+ {
+ "login": "jeffmcaffer",
+ "name": "Jeff McAffer",
+ "avatar_url": "https://avatars2.githubusercontent.com/u/10070956?v=4",
+ "profile": "https://mcaffer.com",
+ "contributions": [
+ "doc"
+ ]
+ },
+ {
+ "login": "tjenkinson",
+ "name": "Tom Jenkinson",
+ "avatar_url": "https://avatars0.githubusercontent.com/u/3259993?v=4",
+ "profile": "https://tjenkinson.me",
+ "contributions": [
+ "code"
+ ]
+ },
+ {
+ "login": "casals",
+ "name": "Arthur Casals",
+ "avatar_url": "https://avatars0.githubusercontent.com/u/785860?v=4",
+ "profile": "https://github.com/casals",
+ "contributions": [
+ "content",
+ "doc"
+ ]
+ },
+ {
+ "login": "Simran-B",
+ "name": "Simran",
+ "avatar_url": "https://avatars3.githubusercontent.com/u/7819991?v=4",
+ "profile": "https://www.arangodb.com/",
+ ]
+ },
+ {
+ "login": "Ruth",
+ "name": "Ruth",
+ "avatar_url": "https://avatars0.githubusercontent.com/u/85029?v=4",
+ "profile": "https://github.com/ruth",
+ "contributions": [
+ "content"
+ ]
+ },
+ {
+ "login": "wi5nia",
+ "name": "Tomasz Wisniewski",
+ "avatar_url": "https://avatars2.githubusercontent.com/u/12593852?v=4",
+ "profile": "http://tomaszwisniewski.com",
+ "contributions": [
+ "doc"
+ ]
+ },
+ {
+ "login": "chiedo",
+ "name": "Chiedo John",
+ "avatar_url": "https://avatars2.githubusercontent.com/u/2156688?v=4",
+ "profile": "https://chiedojohn.com/",
+ "contributions": [
+ "code"
+ ]
}
],
"contributorsPerLine": 7,
@@ -294,4 +365,4 @@
"repoHost": "https://github.com",
"skipCi": true,
"commitConvention": "none"
-}
\ No newline at end of file
+}
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index bebc3f7218c9..eb71a6edef7a 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -14,3 +14,7 @@ package-lock.json @github/docs-engineering
package.json @github/docs-engineering
/content/github/site-policy/ @github/site-policy-admins
+
+# Make sure that Octokit maintainers get notified about changes
+# relevant to the Octokit libraries (https://github.com/octokit)
+/content/rest/reference @github/octokit-maintainers
diff --git a/.github/allowed-actions.js b/.github/allowed-actions.js
index f9ce4ab37005..66c06473dce2 100644
--- a/.github/allowed-actions.js
+++ b/.github/allowed-actions.js
@@ -8,6 +8,7 @@ module.exports = [
'actions/cache@v2',
'actions/checkout@v2',
'actions/github-script@0.9.0',
+ 'actions/github-script@v2.0.0',
'actions/github-script@v2',
'actions/github-script@v3',
'actions/labeler@v2',
@@ -22,11 +23,14 @@ module.exports = [
'juliangruber/approve-pull-request-action@v1',
'juliangruber/find-pull-request-action@v1',
'juliangruber/read-file-action@v1',
- 'pascalgn/automerge-action@135f0bdb927d9807b5446f7ca9ecc2c51de03c4a',
+ 'pascalgn/automerge-action@c9bd182',
'peter-evans/create-issue-from-file@v2',
'peter-evans/create-pull-request@v2',
+ 'rachmari/actions-add-new-issue-to-column@v1.1.1',
+ 'rachmari/labeler@v1.0.4',
'repo-sync/github-sync@v2',
'repo-sync/pull-request@v2',
'rtCamp/action-slack-notify@master',
- 'rtCamp/action-slack-notify@v2.1.0'
-]
\ No newline at end of file
+ 'rtCamp/action-slack-notify@v2.1.0',
+ 'tjenkinson/gh-action-auto-merge-dependency-updates@cee2ac0'
+]
diff --git a/.github/workflows/automerge-dependencies.yml b/.github/workflows/automerge-dependencies.yml
new file mode 100644
index 000000000000..9650706fce12
--- /dev/null
+++ b/.github/workflows/automerge-dependencies.yml
@@ -0,0 +1,14 @@
+name: Auto Merge Dependency Updates
+
+on:
+ - pull_request
+ - pull_request_review
+
+jobs:
+ run:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: tjenkinson/gh-action-auto-merge-dependency-updates@cee2ac0
+ with:
+ repo-token: ${{ secrets.GITHUB_TOKEN }}
+ allowed-actors: dependabot[bot]
diff --git a/.github/workflows/automerge.yml b/.github/workflows/automerge.yml
index be58649fc820..a581bfb68fe3 100644
--- a/.github/workflows/automerge.yml
+++ b/.github/workflows/automerge.yml
@@ -20,18 +20,17 @@ on:
jobs:
automerge:
runs-on: ubuntu-latest
- if: contains(github.event.pull_request.labels.*.name, 'automerge')
+ if: contains(github.event.pull_request.labels.*.name, 'automerge') || contains(github.event.pull_request.labels.*.name, 'autosquash')
steps:
- name: automerge
- uses: "pascalgn/automerge-action@135f0bdb927d9807b5446f7ca9ecc2c51de03c4a"
+ uses: "pascalgn/automerge-action@c9bd182"
env:
GITHUB_TOKEN: "${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }}"
- MERGE_LABELS: "automerge"
- MERGE_REMOVE_LABELS: ""
+ MERGE_METHOD_LABELS: "automerge=merge,autosquash=squash"
MERGE_COMMIT_MESSAGE: "pull-request-title"
MERGE_METHOD: "merge"
MERGE_FORKS: "true"
MERGE_RETRIES: "50"
- MERGE_RETRY_SLEEP: "10000"
- UPDATE_LABELS: "automerge"
+ MERGE_RETRY_SLEEP: "10000" # ten seconds
+ UPDATE_LABELS: "automerge,autosquash"
UPDATE_METHOD: "merge"
diff --git a/.github/workflows/autosquash.yml b/.github/workflows/autosquash.yml
deleted file mode 100644
index 2ff83b152fc2..000000000000
--- a/.github/workflows/autosquash.yml
+++ /dev/null
@@ -1,37 +0,0 @@
-name: autosquash
-on:
- pull_request:
- types:
- - labeled
- - unlabeled
- - synchronize
- - opened
- - edited
- - ready_for_review
- - reopened
- - unlocked
- pull_request_review:
- types:
- - submitted
- check_suite:
- types:
- - completed
- status: {}
-jobs:
- automerge:
- runs-on: ubuntu-latest
- if: contains(github.event.pull_request.labels.*.name, 'autosquash')
- steps:
- - name: autosquash
- uses: "pascalgn/automerge-action@135f0bdb927d9807b5446f7ca9ecc2c51de03c4a"
- env:
- GITHUB_TOKEN: "${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }}"
- MERGE_LABELS: "autosquash"
- MERGE_REMOVE_LABELS: ""
- MERGE_COMMIT_MESSAGE: "pull-request-title"
- MERGE_METHOD: "squash"
- MERGE_FORKS: "true"
- MERGE_RETRIES: "50"
- MERGE_RETRY_SLEEP: "10000"
- UPDATE_LABELS: "automerge"
- UPDATE_METHOD: "merge"
diff --git a/.github/workflows/merged-notification.yml b/.github/workflows/merged-notification.yml
index 7cc62bc58b4a..2251541a639e 100644
--- a/.github/workflows/merged-notification.yml
+++ b/.github/workflows/merged-notification.yml
@@ -13,11 +13,7 @@ jobs:
github.issues.createComment({
...context.repo,
issue_number: context.payload.pull_request.number,
- body: `Thanks very much for contributing! Your pull request has been merged ๐ You should see your changes appear on the site in approximately 24 hours. To add your โจ contribution to the README.md, create a new comment in this PR with:
-
- ```
- @all-contributors please add @${context.payload.pull_request.user.login} for docs
- ```
-
- If you want to, you can use the [emoji key](https://allcontributors.org/docs/en/emoji-key) to replace docs with a different contribution type.`
+ body: `Thanks very much for contributing! Your pull request has been merged ๐ You should see your changes appear on the site in approximately 24 hours.
+
+ If you haven't already, you can add yourself to [the list of contributors](https://github.com/github/docs#contributors-) by creating a new comment in this PR using [these instructions](https://allcontributors.org/docs/en/bot/usage#commands). Thanks again! :sparkles:`
})
diff --git a/.github/workflows/npm-publish.yml b/.github/workflows/npm-publish.yml
new file mode 100644
index 000000000000..861e37239f22
--- /dev/null
+++ b/.github/workflows/npm-publish.yml
@@ -0,0 +1,47 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
+
+name: Node.js Package
+
+on:
+ release:
+ types: [created]
+
+jobs:
+ build:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v2
+ - uses: actions/setup-node@v1
+ with:
+ node-version: 12
+ - run: npm ci
+ - run: npm test
+
+ publish-npm:
+ needs: build
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v2
+ - uses: actions/setup-node@v1
+ with:
+ node-version: 12
+ registry-url: https://registry.npmjs.org/
+ - run: npm ci
+ - run: npm publish
+ env:
+ NODE_AUTH_TOKEN: ${{secrets.npm_token}}
+
+ publish-gpr:
+ needs: build
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v2
+ - uses: actions/setup-node@v1
+ with:
+ node-version: 12
+ registry-url: https://npm.pkg.github.com/
+ - run: npm ci
+ - run: npm publish
+ env:
+ NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}
diff --git a/.github/workflows/start-new-engineering-pr-workflow.yml b/.github/workflows/start-new-engineering-pr-workflow.yml
index 29f076d5044f..03d75ccda9e8 100644
--- a/.github/workflows/start-new-engineering-pr-workflow.yml
+++ b/.github/workflows/start-new-engineering-pr-workflow.yml
@@ -6,7 +6,6 @@ on:
jobs:
triage:
- if: github.repository == 'github/docs-internal'
runs-on: ubuntu-latest
continue-on-error: true
env:
@@ -15,6 +14,7 @@ jobs:
steps:
- name:
uses: actions/github-script@v2
+ continue-on-error: true
with:
github-token: ${{ secrets.DOCUBOT_FR_PROJECT_BOARD_WORKFLOWS_REPO_ORG_READ_SCOPES }}
script: |
diff --git a/.github/workflows/test-windows.yml b/.github/workflows/test-windows.yml
index 649df7a1c31a..f2d845b30e23 100644
--- a/.github/workflows/test-windows.yml
+++ b/.github/workflows/test-windows.yml
@@ -3,6 +3,7 @@
name: Node.js Tests - Windows
on:
+ workflow_dispatch:
schedule:
- cron: "50 19 * * *" # once a day at 19:50 UTC / 11:50 PST
@@ -11,7 +12,6 @@ env:
jobs:
lint:
- if: github.repository == 'github/docs-internal'
runs-on: windows-latest
steps:
- name: Check out repo
@@ -45,7 +45,6 @@ jobs:
run: npm run check-deps
test:
- if: github.repository == 'github/docs-internal'
runs-on: windows-latest
strategy:
fail-fast: false
diff --git a/.github/workflows/triage-issue-comments.yml b/.github/workflows/triage-issue-comments.yml
index f14b7128e77a..ac1e4494134c 100644
--- a/.github/workflows/triage-issue-comments.yml
+++ b/.github/workflows/triage-issue-comments.yml
@@ -33,13 +33,13 @@ jobs:
return 'false'
}
- name: Label issues with new comments with 'triage'
- uses: andymckay/labeler@1.0.2
+ uses: rachmari/labeler@v1.0.4
if: (steps.is-internal-contributor.outputs.result == 'false')
with:
repo-token: "${{ secrets.GITHUB_TOKEN }}"
add-labels: "triage"
- name: Triage to project board
- uses: konradpabjan/actions-add-new-issue-to-column@v1.1
+ uses: rachmari/actions-add-new-issue-to-column@v1.1.1
with:
action-token: ${{ secrets.GITHUB_TOKEN }}
project-url: "https://github.com/github/docs/projects/1"
diff --git a/.github/workflows/triage-issues.yml b/.github/workflows/triage-issues.yml
index 070f59891ce5..6bf0888eec6e 100644
--- a/.github/workflows/triage-issues.yml
+++ b/.github/workflows/triage-issues.yml
@@ -10,12 +10,12 @@ jobs:
steps:
- name: Label new issues with 'triage'
- uses: andymckay/labeler@1.0.2
+ uses: rachmari/labeler@v1.0.4
with:
repo-token: "${{ secrets.GITHUB_TOKEN }}"
add-labels: "triage"
- name: Triage to project board
- uses: konradpabjan/actions-add-new-issue-to-column@v1.1
+ uses: rachmari/actions-add-new-issue-to-column@v1.1.1
with:
action-token: ${{ secrets.GITHUB_TOKEN }}
project-url: "https://github.com/github/docs/projects/1"
diff --git a/.github/workflows/triage-pull-requests.yml b/.github/workflows/triage-pull-requests.yml
index 71d6d343dab7..778d6a111071 100644
--- a/.github/workflows/triage-pull-requests.yml
+++ b/.github/workflows/triage-pull-requests.yml
@@ -4,18 +4,18 @@ on:
types: [reopened, opened]
jobs:
- triage_issues:
+ triage_pulls:
if: github.repository == 'github/docs'
runs-on: ubuntu-latest
steps:
- name: Label new pull requests with 'triage'
- uses: andymckay/labeler@1.0.2
+ uses: rachmari/labeler@v1.0.4
with:
repo-token: "${{ secrets.GITHUB_TOKEN }}"
add-labels: "triage"
- name: Triage to project board
- uses: konradpabjan/actions-add-new-issue-to-column@v1.1
+ uses: rachmari/actions-add-new-issue-to-column@v1.1.1
with:
action-token: ${{ secrets.GITHUB_TOKEN }}
project-url: "https://github.com/github/docs/projects/1"
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0a15ad19a29c..673610d48848 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -32,7 +32,7 @@ Fork using the command line:
### Make your update:
Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-githubdocs-repository).
- Are you making changes to the application code? You'll need **Node.js v14** to run the site locally. See [contributing/development.md](contributing/development.md).
- - Are you contributing to markdown? We use [GitHub Markdown](contributing/content-markup-reference).
+ - Are you contributing to markdown? We use [GitHub Markdown](contributing/content-markup-reference.md).
### Open a pull request
When you're done making changes and you'd like to propose them for review, use the [pull request template](#pull-request-template) to open your PR (pull request).
@@ -63,8 +63,6 @@ Now that you're a part of the GitHub Docs community, you can keep participating
- [Starting with an issue](#starting-with-an-issue)
- [Labels](#labels)
- [Opening a pull request](#opening-a-pull-request)
- - [Fork using GitHub Desktop](#fork-using-github-desktop)
- - [Fork using the command line](#fork-using-the-command-line)
- [Working in the github/docs repository](#working-in-the-githubdocs-repository)
- [Resolving merge conflicts](#resolving-merge-conflicts)
- [In the GitHub user interface](#in-the-github-user-interface)
@@ -156,7 +154,7 @@ You should always review your own PR first.
For content changes, make sure that you:
- [ ] Confirm that the changes address every part of the content strategy plan from your issue (if there are differences, explain them).
- [ ] Review the content for technical accuracy.
-- [ ] Review the entire pull request using the [localization checklist](contribution/localization-checklist.md).
+- [ ] Review the entire pull request using the [localization checklist](contributing/localization-checklist.md).
- [ ] Copy-edit the changes for grammar, spelling, and adherence to the style guide.
- [ ] Check new or updated Liquid statements to confirm that versioning is correct.
- [ ] Check that all of your changes render correctly in staging. Remember, that lists and tables can be tricky.
diff --git a/LICENSE b/LICENSE
index b50625eb6394..9238c8f93880 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,21 +1,386 @@
-MIT License
-
-Copyright (c) 2020 GitHub
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Attribution 4.0 International
+
+=======================================================================
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and
+does not provide legal services or legal advice. Distribution of
+Creative Commons public licenses does not create a lawyer-client or
+other relationship. Creative Commons makes its licenses and related
+information available on an "as-is" basis. Creative Commons gives no
+warranties regarding its licenses, any material licensed under their
+terms and conditions, or any related information. Creative Commons
+disclaims all liability for damages resulting from their use to the
+fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and
+conditions that creators and other rights holders may use to share
+original works of authorship and other material subject to copyright
+and certain other rights specified in the public license below. The
+following considerations are for informational purposes only, are not
+exhaustive, and do not form part of our licenses.
+
+ Considerations for licensors: Our public licenses are
+ intended for use by those authorized to give the public
+ permission to use material in ways otherwise restricted by
+ copyright and certain other rights. Our licenses are
+ irrevocable. Licensors should read and understand the terms
+ and conditions of the license they choose before applying it.
+ Licensors should also secure all rights necessary before
+ applying our licenses so that the public can reuse the
+ material as expected. Licensors should clearly mark any
+ material not subject to the license. This includes other CC-
+ licensed material, or material used under an exception or
+ limitation to copyright. More considerations for licensors:
+ wiki.creativecommons.org/Considerations_for_licensors
+
+ Considerations for the public: By using one of our public
+ licenses, a licensor grants the public permission to use the
+ licensed material under specified terms and conditions. If
+ the licensor's permission is not necessary for any reason--for
+ example, because of any applicable exception or limitation to
+ copyright--then that use is not regulated by the license. Our
+ licenses grant only permissions under copyright and certain
+ other rights that a licensor has authority to grant. Use of
+ the licensed material may still be restricted for other
+ reasons, including because others have copyright or other
+ rights in the material. A licensor may make special requests,
+ such as asking that all changes be marked or described.
+ Although not required by our licenses, you are encouraged to
+ respect those requests where reasonable. More considerations
+ for the public:
+ wiki.creativecommons.org/Considerations_for_licensees
+
+=======================================================================
+
+Creative Commons Attribution 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree
+to be bound by the terms and conditions of this Creative Commons
+Attribution 4.0 International Public License ("Public License"). To the
+extent this Public License may be interpreted as a contract, You are
+granted the Licensed Rights in consideration of Your acceptance of
+these terms and conditions, and the Licensor grants You such rights in
+consideration of benefits the Licensor receives from making the
+Licensed Material available under these terms and conditions.
+
+Section 1 -- Definitions.
+
+ a. Adapted Material means material subject to Copyright and Similar
+ Rights that is derived from or based upon the Licensed Material
+ and in which the Licensed Material is translated, altered,
+ arranged, transformed, or otherwise modified in a manner requiring
+ permission under the Copyright and Similar Rights held by the
+ Licensor. For purposes of this Public License, where the Licensed
+ Material is a musical work, performance, or sound recording,
+ Adapted Material is always produced where the Licensed Material is
+ synched in timed relation with a moving image.
+
+ b. Adapter's License means the license You apply to Your Copyright
+ and Similar Rights in Your contributions to Adapted Material in
+ accordance with the terms and conditions of this Public License.
+
+ c. Copyright and Similar Rights means copyright and/or similar rights
+ closely related to copyright including, without limitation,
+ performance, broadcast, sound recording, and Sui Generis Database
+ Rights, without regard to how the rights are labeled or
+ categorized. For purposes of this Public License, the rights
+ specified in Section 2(b)(1)-(2) are not Copyright and Similar
+ Rights.
+
+ d. Effective Technological Measures means those measures that, in the
+ absence of proper authority, may not be circumvented under laws
+ fulfilling obligations under Article 11 of the WIPO Copyright
+ Treaty adopted on December 20, 1996, and/or similar international
+ agreements.
+
+ e. Exceptions and Limitations means fair use, fair dealing, and/or
+ any other exception or limitation to Copyright and Similar Rights
+ that applies to Your use of the Licensed Material.
+
+ f. Licensed Material means the artistic or literary work, database,
+ or other material to which the Licensor applied this Public
+ License.
+
+ g. Licensed Rights means the rights granted to You subject to the
+ terms and conditions of this Public License, which are limited to
+ all Copyright and Similar Rights that apply to Your use of the
+ Licensed Material and that the Licensor has authority to license.
+
+ h. Licensor means the individual(s) or entity(ies) granting rights
+ under this Public License.
+
+ i. Share means to provide material to the public by any means or
+ process that requires permission under the Licensed Rights, such
+ as reproduction, public display, public performance, distribution,
+ dissemination, communication, or importation, and to make material
+ available to the public including in ways that members of the
+ public may access the material from a place and at a time
+ individually chosen by them.
+
+ j. Sui Generis Database Rights means rights other than copyright
+ resulting from Directive 96/9/EC of the European Parliament and of
+ the Council of 11 March 1996 on the legal protection of databases,
+ as amended and/or succeeded, as well as other essentially
+ equivalent rights anywhere in the world.
+
+ k. You means the individual or entity exercising the Licensed Rights
+ under this Public License. Your has a corresponding meaning.
+
+Section 2 -- Scope.
+
+ a. License grant.
+
+ 1. Subject to the terms and conditions of this Public License,
+ the Licensor hereby grants You a worldwide, royalty-free,
+ non-sublicensable, non-exclusive, irrevocable license to
+ exercise the Licensed Rights in the Licensed Material to:
+
+ a. reproduce and Share the Licensed Material, in whole or
+ in part; and
+
+ b. produce, reproduce, and Share Adapted Material.
+
+ 2. Exceptions and Limitations. For the avoidance of doubt, where
+ Exceptions and Limitations apply to Your use, this Public
+ License does not apply, and You do not need to comply with
+ its terms and conditions.
+
+ 3. Term. The term of this Public License is specified in Section
+ 6(a).
+
+ 4. Media and formats; technical modifications allowed. The
+ Licensor authorizes You to exercise the Licensed Rights in
+ all media and formats whether now known or hereafter created,
+ and to make technical modifications necessary to do so. The
+ Licensor waives and/or agrees not to assert any right or
+ authority to forbid You from making technical modifications
+ necessary to exercise the Licensed Rights, including
+ technical modifications necessary to circumvent Effective
+ Technological Measures. For purposes of this Public License,
+ simply making modifications authorized by this Section 2(a)
+ (4) never produces Adapted Material.
+
+ 5. Downstream recipients.
+
+ a. Offer from the Licensor -- Licensed Material. Every
+ recipient of the Licensed Material automatically
+ receives an offer from the Licensor to exercise the
+ Licensed Rights under the terms and conditions of this
+ Public License.
+
+ b. No downstream restrictions. You may not offer or impose
+ any additional or different terms or conditions on, or
+ apply any Effective Technological Measures to, the
+ Licensed Material if doing so restricts exercise of the
+ Licensed Rights by any recipient of the Licensed
+ Material.
+
+ 6. No endorsement. Nothing in this Public License constitutes or
+ may be construed as permission to assert or imply that You
+ are, or that Your use of the Licensed Material is, connected
+ with, or sponsored, endorsed, or granted official status by,
+ the Licensor or others designated to receive attribution as
+ provided in Section 3(a)(1)(A)(i).
+
+ b. Other rights.
+
+ 1. Moral rights, such as the right of integrity, are not
+ licensed under this Public License, nor are publicity,
+ privacy, and/or other similar personality rights; however, to
+ the extent possible, the Licensor waives and/or agrees not to
+ assert any such rights held by the Licensor to the limited
+ extent necessary to allow You to exercise the Licensed
+ Rights, but not otherwise.
+
+ 2. Patent and trademark rights are not licensed under this
+ Public License.
+
+ 3. To the extent possible, the Licensor waives any right to
+ collect royalties from You for the exercise of the Licensed
+ Rights, whether directly or through a collecting society
+ under any voluntary or waivable statutory or compulsory
+ licensing scheme. In all other cases the Licensor expressly
+ reserves any right to collect such royalties.
+
+Section 3 -- License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the
+following conditions.
+
+ a. Attribution.
+
+ 1. If You Share the Licensed Material (including in modified
+ form), You must:
+
+ a. retain the following if it is supplied by the Licensor
+ with the Licensed Material:
+
+ i. identification of the creator(s) of the Licensed
+ Material and any others designated to receive
+ attribution, in any reasonable manner requested by
+ the Licensor (including by pseudonym if
+ designated);
+
+ ii. a copyright notice;
+
+ iii. a notice that refers to this Public License;
+
+ iv. a notice that refers to the disclaimer of
+ warranties;
+
+ v. a URI or hyperlink to the Licensed Material to the
+ extent reasonably practicable;
+
+ b. indicate if You modified the Licensed Material and
+ retain an indication of any previous modifications; and
+
+ c. indicate the Licensed Material is licensed under this
+ Public License, and include the text of, or the URI or
+ hyperlink to, this Public License.
+
+ 2. You may satisfy the conditions in Section 3(a)(1) in any
+ reasonable manner based on the medium, means, and context in
+ which You Share the Licensed Material. For example, it may be
+ reasonable to satisfy the conditions by providing a URI or
+ hyperlink to a resource that includes the required
+ information.
+
+ 3. If requested by the Licensor, You must remove any of the
+ information required by Section 3(a)(1)(A) to the extent
+ reasonably practicable.
+
+ 4. If You Share Adapted Material You produce, the Adapter's
+ License You apply must not prevent recipients of the Adapted
+ Material from complying with this Public License.
+
+Section 4 -- Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that
+apply to Your use of the Licensed Material:
+
+ a. for the avoidance of doubt, Section 2(a)(1) grants You the right
+ to extract, reuse, reproduce, and Share all or a substantial
+ portion of the contents of the database;
+
+ b. if You include all or a substantial portion of the database
+ contents in a database in which You have Sui Generis Database
+ Rights, then the database in which You have Sui Generis Database
+ Rights (but not its individual contents) is Adapted Material; and
+
+ c. You must comply with the conditions in Section 3(a) if You Share
+ all or a substantial portion of the contents of the database.
+
+For the avoidance of doubt, this Section 4 supplements and does not
+replace Your obligations under this Public License where the Licensed
+Rights include other Copyright and Similar Rights.
+
+Section 5 -- Disclaimer of Warranties and Limitation of Liability.
+
+ a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
+ EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
+ AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
+ ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
+ IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
+ WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
+ PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
+ ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
+ KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
+ ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
+
+ b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
+ TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
+ NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
+ INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
+ COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
+ USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
+ ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
+ DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
+ IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
+
+ c. The disclaimer of warranties and limitation of liability provided
+ above shall be interpreted in a manner that, to the extent
+ possible, most closely approximates an absolute disclaimer and
+ waiver of all liability.
+
+Section 6 -- Term and Termination.
+
+ a. This Public License applies for the term of the Copyright and
+ Similar Rights licensed here. However, if You fail to comply with
+ this Public License, then Your rights under this Public License
+ terminate automatically.
+
+ b. Where Your right to use the Licensed Material has terminated under
+ Section 6(a), it reinstates:
+
+ 1. automatically as of the date the violation is cured, provided
+ it is cured within 30 days of Your discovery of the
+ violation; or
+
+ 2. upon express reinstatement by the Licensor.
+
+ For the avoidance of doubt, this Section 6(b) does not affect any
+ right the Licensor may have to seek remedies for Your violations
+ of this Public License.
+
+ c. For the avoidance of doubt, the Licensor may also offer the
+ Licensed Material under separate terms or conditions or stop
+ distributing the Licensed Material at any time; however, doing so
+ will not terminate this Public License.
+
+ d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
+ License.
+
+Section 7 -- Other Terms and Conditions.
+
+ a. The Licensor shall not be bound by any additional or different
+ terms or conditions communicated by You unless expressly agreed.
+
+ b. Any arrangements, understandings, or agreements regarding the
+ Licensed Material not stated herein are separate from and
+ independent of the terms and conditions of this Public License.
+
+Section 8 -- Interpretation.
+
+ a. For the avoidance of doubt, this Public License does not, and
+ shall not be interpreted to, reduce, limit, restrict, or impose
+ conditions on any use of the Licensed Material that could lawfully
+ be made without permission under this Public License.
+
+ b. To the extent possible, if any provision of this Public License is
+ deemed unenforceable, it shall be automatically reformed to the
+ minimum extent necessary to make it enforceable. If the provision
+ cannot be reformed, it shall be severed from this Public License
+ without affecting the enforceability of the remaining terms and
+ conditions.
+
+ c. No term or condition of this Public License will be waived and no
+ failure to comply consented to unless expressly agreed to by the
+ Licensor.
+
+ d. Nothing in this Public License constitutes or may be interpreted
+ as a limitation upon, or waiver of, any privileges and immunities
+ that apply to the Licensor or You, including from the legal
+ processes of any jurisdiction or authority.
+
+=======================================================================
+
+Creative Commons is not a party to its public
+licenses. Notwithstanding, Creative Commons may elect to apply one of
+its public licenses to material it publishes and in those instances
+will be considered the โLicensor.โ The text of the Creative Commons
+public licenses is dedicated to the public domain under the CC0 Public
+Domain Dedication. Except for the limited purpose of indicating that
+material is shared under a Creative Commons public license or as
+otherwise permitted by the Creative Commons policies published at
+creativecommons.org/policies, Creative Commons does not authorize the
+use of the trademark "Creative Commons" or any other trademark or logo
+of Creative Commons without its prior written consent including,
+without limitation, in connection with any unauthorized modifications
+to any of its public licenses or any other arrangements,
+understandings, or agreements concerning use of licensed material. For
+the avoidance of doubt, this paragraph does not form part of the
+public licenses.
+
+Creative Commons may be contacted at creativecommons.org.
diff --git a/LICENSE-CODE b/LICENSE-CODE
new file mode 100644
index 000000000000..b50625eb6394
--- /dev/null
+++ b/LICENSE-CODE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020 GitHub
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
index b0d43312450d..6f1b4d644c0c 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
## GitHub Docs
-This repository contains the documentation website code and Markdown source files for docs.github.com.
+This repository contains the documentation website code and Markdown source files for [docs.github.com](https://docs.github.com).
GitHub's Docs team works on pre-production content in a private repo that regularly syncs with this public repo.
@@ -26,6 +26,10 @@ As you're using the GitHub Docs, you may find something in an article that you'd
If you've found a problem, you can open an issue using a [template](https://github.com/github/docs/issues/new/choose).
+#### Solve an issue
+
+If you have a solution to one of the open issues, you will need to fork the repository and submit a PR using the [template](https://github.com/github/docs/blob/main/CONTRIBUTING.md#pull-request-template) that is visible automatically in the pull request body. For more details about this process, please check out [Getting Started with Contributing](/CONTRIBUTING.md).
+
#### Join us in discussions
We use GitHub Discussions to talk about all sorts of topics related to documentation and this site. For example: if you'd like help troubleshooting a PR, have a great new idea, or want to share something amazing you've learned in our docs, join us in [discussions](https://github.com/github/docs/discussions).
@@ -61,9 +65,9 @@ In addition to the README you're reading right now, this repo includes other REA
## License
-The GitHub product documentation in the assets, content, and data folders are licensed under a [CC-BY license](content/LICENSE).
+The GitHub product documentation in the assets, content, and data folders are licensed under a [CC-BY license](LICENSE).
-All other code in this repository is licensed under a [MIT license](LICENSE).
+All other code in this repository is licensed under a [MIT license](LICENSE-CODE).
When using the GitHub logos, be sure to follow the [GitHub logo guidelines](https://github.com/logos).
@@ -111,10 +115,29 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
Vanessa Yuen ๐ ๐ป |
Zeke Sikelianos ๐ ๐ป |
+
+ Benjamin Nickolls ๐ |
+ Jeff McAffer ๐ |
+ Tom Jenkinson ๐ป |
+ Arthur Casals ๐ ๐ |
+ Ruth ๐ |
+ Tomasz Wisniewski ๐ |
+ Chiedo John ๐ป |
+
+
+ Benjamin Nickolls ๐ |
+ Jeff McAffer ๐ |
+ Tom Jenkinson ๐ป |
+ Arthur Casals ๐ ๐ |
+ Simran ๐ |
+ Ruth ๐ |
+ Tomasz Wisniewski ๐ |
+
+
This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!
diff --git a/assets/images/commit-workflow-file.png b/assets/images/commit-workflow-file.png
index 3a358304b718..d17769ff418c 100644
Binary files a/assets/images/commit-workflow-file.png and b/assets/images/commit-workflow-file.png differ
diff --git a/assets/images/contribution_cta.png b/assets/images/contribution_cta.png
index 59bb7374de13..eb02fe6ca354 100644
Binary files a/assets/images/contribution_cta.png and b/assets/images/contribution_cta.png differ
diff --git a/assets/images/help/branch/branch-rename-edit.png b/assets/images/help/branch/branch-rename-edit.png
index 72862bdcb270..7f21862c390a 100644
Binary files a/assets/images/help/branch/branch-rename-edit.png and b/assets/images/help/branch/branch-rename-edit.png differ
diff --git a/assets/images/help/branch/branch-rename-rename.png b/assets/images/help/branch/branch-rename-rename.png
index 1f5bef6f809c..5d870c27a012 100644
Binary files a/assets/images/help/branch/branch-rename-rename.png and b/assets/images/help/branch/branch-rename-rename.png differ
diff --git a/assets/images/help/branch/branch-rename-type.png b/assets/images/help/branch/branch-rename-type.png
index 1265f6674e75..cac66ee45bf4 100644
Binary files a/assets/images/help/branch/branch-rename-type.png and b/assets/images/help/branch/branch-rename-type.png differ
diff --git a/assets/images/help/business-accounts/billing-license-info.png b/assets/images/help/business-accounts/billing-license-info.png
index 2e3c119f948b..a5c10f33ddca 100644
Binary files a/assets/images/help/business-accounts/billing-license-info.png and b/assets/images/help/business-accounts/billing-license-info.png differ
diff --git a/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png b/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png
index 54fa46956f5c..7c3be5c4b01a 100644
Binary files a/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png and b/assets/images/help/codespaces/connect-to-github-codespaces-preview-feature.png differ
diff --git a/assets/images/help/codespaces/visual-studio-codespace-details.png b/assets/images/help/codespaces/visual-studio-codespace-details.png
index 33da0db17f63..302cd1ce3ec6 100644
Binary files a/assets/images/help/codespaces/visual-studio-codespace-details.png and b/assets/images/help/codespaces/visual-studio-codespace-details.png differ
diff --git a/assets/images/help/codespaces/visual-studio-connect-codespace.png b/assets/images/help/codespaces/visual-studio-connect-codespace.png
index 3181a5ae6c88..db365d24fc72 100644
Binary files a/assets/images/help/codespaces/visual-studio-connect-codespace.png and b/assets/images/help/codespaces/visual-studio-connect-codespace.png differ
diff --git a/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png b/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png
index 3f1a7f288a87..ada5429ebf20 100644
Binary files a/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png and b/assets/images/help/codespaces/visual-studio-eshoponweb-codespace.png differ
diff --git a/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png b/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png
index 16d85ebfcfb5..f8286d970344 100644
Binary files a/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png and b/assets/images/help/codespaces/visual-studio-file-connect-to-codespace.png differ
diff --git a/assets/images/help/codespaces/visual-studio-sign-in-to-github.png b/assets/images/help/codespaces/visual-studio-sign-in-to-github.png
index 75d86ead8c0f..f88108965cb9 100644
Binary files a/assets/images/help/codespaces/visual-studio-sign-in-to-github.png and b/assets/images/help/codespaces/visual-studio-sign-in-to-github.png differ
diff --git a/assets/images/help/codespaces/visual-studio-start-window.png b/assets/images/help/codespaces/visual-studio-start-window.png
index a17388e15bb3..55d9d29bc2b2 100644
Binary files a/assets/images/help/codespaces/visual-studio-start-window.png and b/assets/images/help/codespaces/visual-studio-start-window.png differ
diff --git a/assets/images/help/enterprises/administrators-pending.png b/assets/images/help/enterprises/administrators-pending.png
index 72fc8bf6a433..5461fa840c60 100644
Binary files a/assets/images/help/enterprises/administrators-pending.png and b/assets/images/help/enterprises/administrators-pending.png differ
diff --git a/assets/images/help/enterprises/members-pending.png b/assets/images/help/enterprises/members-pending.png
index 8717cd130703..30fca5396547 100644
Binary files a/assets/images/help/enterprises/members-pending.png and b/assets/images/help/enterprises/members-pending.png differ
diff --git a/assets/images/help/enterprises/your-enterprises-list.png b/assets/images/help/enterprises/your-enterprises-list.png
index a30d5a8b31fc..4229f6fd0933 100644
Binary files a/assets/images/help/enterprises/your-enterprises-list.png and b/assets/images/help/enterprises/your-enterprises-list.png differ
diff --git a/assets/images/help/enterprises/your-enterprises.png b/assets/images/help/enterprises/your-enterprises.png
index 39010150b4c2..6b9339836c04 100644
Binary files a/assets/images/help/enterprises/your-enterprises.png and b/assets/images/help/enterprises/your-enterprises.png differ
diff --git a/assets/images/help/images/learn-github-actions-repository.png b/assets/images/help/images/learn-github-actions-repository.png
index 75efec19ed65..2ecc7d126de1 100644
Binary files a/assets/images/help/images/learn-github-actions-repository.png and b/assets/images/help/images/learn-github-actions-repository.png differ
diff --git a/assets/images/help/images/learn-github-actions-run.png b/assets/images/help/images/learn-github-actions-run.png
index 0ab2b6f5770f..f2bc2ff7cb83 100644
Binary files a/assets/images/help/images/learn-github-actions-run.png and b/assets/images/help/images/learn-github-actions-run.png differ
diff --git a/assets/images/help/images/learn-github-actions-workflow.png b/assets/images/help/images/learn-github-actions-workflow.png
index 5966062104c3..df9eba64d40a 100644
Binary files a/assets/images/help/images/learn-github-actions-workflow.png and b/assets/images/help/images/learn-github-actions-workflow.png differ
diff --git a/assets/images/help/images/overview-actions-design.png b/assets/images/help/images/overview-actions-design.png
index 4e844ddf3bf4..67ed2a6d8b29 100644
Binary files a/assets/images/help/images/overview-actions-design.png and b/assets/images/help/images/overview-actions-design.png differ
diff --git a/assets/images/help/images/overview-actions-event.png b/assets/images/help/images/overview-actions-event.png
index 7f632c016f7f..fe837bf2f301 100644
Binary files a/assets/images/help/images/overview-actions-event.png and b/assets/images/help/images/overview-actions-event.png differ
diff --git a/assets/images/help/images/overview-actions-result.png b/assets/images/help/images/overview-actions-result.png
index 43026f1fbe7e..d469642450f7 100644
Binary files a/assets/images/help/images/overview-actions-result.png and b/assets/images/help/images/overview-actions-result.png differ
diff --git a/assets/images/help/images/overview-actions-simple.png b/assets/images/help/images/overview-actions-simple.png
index 421e790f646f..b468bbd80ed4 100644
Binary files a/assets/images/help/images/overview-actions-simple.png and b/assets/images/help/images/overview-actions-simple.png differ
diff --git a/assets/images/help/organizations/actions-policy-allow-list.png b/assets/images/help/organizations/actions-policy-allow-list.png
index 0acf374032b3..4783ef62b607 100644
Binary files a/assets/images/help/organizations/actions-policy-allow-list.png and b/assets/images/help/organizations/actions-policy-allow-list.png differ
diff --git a/assets/images/help/organizations/actions-policy.png b/assets/images/help/organizations/actions-policy.png
index ef2c6c507168..a88ca70a35ca 100644
Binary files a/assets/images/help/organizations/actions-policy.png and b/assets/images/help/organizations/actions-policy.png differ
diff --git a/assets/images/help/organizations/enterprise-actions-policy-allow-list.png b/assets/images/help/organizations/enterprise-actions-policy-allow-list.png
index 3eadd8452f78..a6d29fe3bff3 100644
Binary files a/assets/images/help/organizations/enterprise-actions-policy-allow-list.png and b/assets/images/help/organizations/enterprise-actions-policy-allow-list.png differ
diff --git a/assets/images/help/organizations/enterprise-actions-policy.png b/assets/images/help/organizations/enterprise-actions-policy.png
index c59c2d4930b1..edb2fa913797 100644
Binary files a/assets/images/help/organizations/enterprise-actions-policy.png and b/assets/images/help/organizations/enterprise-actions-policy.png differ
diff --git a/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png b/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png
index 2a3b984e63cd..66359c006431 100644
Binary files a/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png and b/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png differ
diff --git a/assets/images/help/organizations/org-settings-pages-disable-publication-save-button.png b/assets/images/help/organizations/org-settings-pages-disable-publication-save-button.png
index 037c5504784c..9f63bff9053c 100644
Binary files a/assets/images/help/organizations/org-settings-pages-disable-publication-save-button.png and b/assets/images/help/organizations/org-settings-pages-disable-publication-save-button.png differ
diff --git a/assets/images/help/repository/actions-delete-artifact.png b/assets/images/help/repository/actions-delete-artifact.png
index c461f3bbeb73..7f8d11549269 100644
Binary files a/assets/images/help/repository/actions-delete-artifact.png and b/assets/images/help/repository/actions-delete-artifact.png differ
diff --git a/assets/images/help/repository/actions-disable-workflow.png b/assets/images/help/repository/actions-disable-workflow.png
index 1e45776a9a03..c62f19e9b3a2 100644
Binary files a/assets/images/help/repository/actions-disable-workflow.png and b/assets/images/help/repository/actions-disable-workflow.png differ
diff --git a/assets/images/help/repository/actions-enable-workflow.png b/assets/images/help/repository/actions-enable-workflow.png
index 3d356e4fe120..ab79895ce42b 100644
Binary files a/assets/images/help/repository/actions-enable-workflow.png and b/assets/images/help/repository/actions-enable-workflow.png differ
diff --git a/assets/images/help/repository/actions-find-disabled-workflow.png b/assets/images/help/repository/actions-find-disabled-workflow.png
index 131c910e6133..a1b5ea4fdec1 100644
Binary files a/assets/images/help/repository/actions-find-disabled-workflow.png and b/assets/images/help/repository/actions-find-disabled-workflow.png differ
diff --git a/assets/images/help/repository/actions-policy-allow-list.png b/assets/images/help/repository/actions-policy-allow-list.png
index a06ae226b4d6..9ae09297eb86 100644
Binary files a/assets/images/help/repository/actions-policy-allow-list.png and b/assets/images/help/repository/actions-policy-allow-list.png differ
diff --git a/assets/images/help/repository/actions-policy.png b/assets/images/help/repository/actions-policy.png
index c29cd3b832d8..69d1a9ca4107 100644
Binary files a/assets/images/help/repository/actions-policy.png and b/assets/images/help/repository/actions-policy.png differ
diff --git a/assets/images/help/repository/actions-select-disabled-workflow.png b/assets/images/help/repository/actions-select-disabled-workflow.png
index 2f274fed70f5..78fcaf652faf 100644
Binary files a/assets/images/help/repository/actions-select-disabled-workflow.png and b/assets/images/help/repository/actions-select-disabled-workflow.png differ
diff --git a/assets/images/help/repository/actions-workflow-menu-kebab.png b/assets/images/help/repository/actions-workflow-menu-kebab.png
index fc7876a6e6f0..823514d35cb6 100644
Binary files a/assets/images/help/repository/actions-workflow-menu-kebab.png and b/assets/images/help/repository/actions-workflow-menu-kebab.png differ
diff --git a/assets/images/help/repository/artifact-drop-down.png b/assets/images/help/repository/artifact-drop-down.png
index cf12247c4c56..8ea00c17b946 100644
Binary files a/assets/images/help/repository/artifact-drop-down.png and b/assets/images/help/repository/artifact-drop-down.png differ
diff --git a/assets/images/help/repository/cancel-check-suite.png b/assets/images/help/repository/cancel-check-suite.png
index cf6513c04f13..3db1bbaadeb7 100644
Binary files a/assets/images/help/repository/cancel-check-suite.png and b/assets/images/help/repository/cancel-check-suite.png differ
diff --git a/assets/images/help/repository/code-scanning-actions-list.png b/assets/images/help/repository/code-scanning-actions-list.png
index 04446c8c97a2..cbd7cb8bb929 100644
Binary files a/assets/images/help/repository/code-scanning-actions-list.png and b/assets/images/help/repository/code-scanning-actions-list.png differ
diff --git a/assets/images/help/repository/code-scanning-alert-close-drop-down.png b/assets/images/help/repository/code-scanning-alert-close-drop-down.png
index a8356bb7e282..92ee682e1c21 100644
Binary files a/assets/images/help/repository/code-scanning-alert-close-drop-down.png and b/assets/images/help/repository/code-scanning-alert-close-drop-down.png differ
diff --git a/assets/images/help/repository/code-scanning-alert.png b/assets/images/help/repository/code-scanning-alert.png
index 07c156777d4a..f2a5b70715fc 100644
Binary files a/assets/images/help/repository/code-scanning-alert.png and b/assets/images/help/repository/code-scanning-alert.png differ
diff --git a/assets/images/help/repository/code-scanning-alerts-found-link.png b/assets/images/help/repository/code-scanning-alerts-found-link.png
index b72d268f23e7..3f6622117c18 100644
Binary files a/assets/images/help/repository/code-scanning-alerts-found-link.png and b/assets/images/help/repository/code-scanning-alerts-found-link.png differ
diff --git a/assets/images/help/repository/code-scanning-branch-dropdown.png b/assets/images/help/repository/code-scanning-branch-dropdown.png
index 91db8bdd1847..d7c7e8914a9a 100644
Binary files a/assets/images/help/repository/code-scanning-branch-dropdown.png and b/assets/images/help/repository/code-scanning-branch-dropdown.png differ
diff --git a/assets/images/help/repository/code-scanning-check-failure.png b/assets/images/help/repository/code-scanning-check-failure.png
index 46488c5bb39f..ec3a5b2928c2 100644
Binary files a/assets/images/help/repository/code-scanning-check-failure.png and b/assets/images/help/repository/code-scanning-check-failure.png differ
diff --git a/assets/images/help/repository/code-scanning-click-alert.png b/assets/images/help/repository/code-scanning-click-alert.png
index fc9f29a2c686..fb52df3b16b2 100644
Binary files a/assets/images/help/repository/code-scanning-click-alert.png and b/assets/images/help/repository/code-scanning-click-alert.png differ
diff --git a/assets/images/help/repository/code-scanning-logging-analyze-action.png b/assets/images/help/repository/code-scanning-logging-analyze-action.png
index 2ce67716e207..d18c217e6479 100644
Binary files a/assets/images/help/repository/code-scanning-logging-analyze-action.png and b/assets/images/help/repository/code-scanning-logging-analyze-action.png differ
diff --git a/assets/images/help/repository/code-scanning-missing-analysis.png b/assets/images/help/repository/code-scanning-missing-analysis.png
index 026134a7d93a..38b9d5b1e612 100644
Binary files a/assets/images/help/repository/code-scanning-missing-analysis.png and b/assets/images/help/repository/code-scanning-missing-analysis.png differ
diff --git a/assets/images/help/repository/code-scanning-pr-alert.png b/assets/images/help/repository/code-scanning-pr-alert.png
index e7057845ce8f..df30d24ae8eb 100644
Binary files a/assets/images/help/repository/code-scanning-pr-alert.png and b/assets/images/help/repository/code-scanning-pr-alert.png differ
diff --git a/assets/images/help/repository/code-scanning-pr-annotation.png b/assets/images/help/repository/code-scanning-pr-annotation.png
index fc15573141ea..400f1c049de7 100644
Binary files a/assets/images/help/repository/code-scanning-pr-annotation.png and b/assets/images/help/repository/code-scanning-pr-annotation.png differ
diff --git a/assets/images/help/repository/code-scanning-pr-checks.png b/assets/images/help/repository/code-scanning-pr-checks.png
index bb2045ac2f8b..cb001e0d2d43 100644
Binary files a/assets/images/help/repository/code-scanning-pr-checks.png and b/assets/images/help/repository/code-scanning-pr-checks.png differ
diff --git a/assets/images/help/repository/code-scanning-set-up-this-workflow.png b/assets/images/help/repository/code-scanning-set-up-this-workflow.png
index f2b0af3b1190..655cbb9d3bd8 100644
Binary files a/assets/images/help/repository/code-scanning-set-up-this-workflow.png and b/assets/images/help/repository/code-scanning-set-up-this-workflow.png differ
diff --git a/assets/images/help/repository/code-scanning-show-paths.png b/assets/images/help/repository/code-scanning-show-paths.png
index 67a0cd5db690..6829ef0e7f7e 100644
Binary files a/assets/images/help/repository/code-scanning-show-paths.png and b/assets/images/help/repository/code-scanning-show-paths.png differ
diff --git a/assets/images/help/repository/delete-all-logs.png b/assets/images/help/repository/delete-all-logs.png
index 5e9046b4da27..dc609c5cd062 100644
Binary files a/assets/images/help/repository/delete-all-logs.png and b/assets/images/help/repository/delete-all-logs.png differ
diff --git a/assets/images/help/repository/download-logs-drop-down.png b/assets/images/help/repository/download-logs-drop-down.png
index cebea7f16fa7..dbba06095b0b 100644
Binary files a/assets/images/help/repository/download-logs-drop-down.png and b/assets/images/help/repository/download-logs-drop-down.png differ
diff --git a/assets/images/help/repository/https-url-clone-cli.png b/assets/images/help/repository/https-url-clone-cli.png
index 2a75b97ac34d..c456ca5075e5 100644
Binary files a/assets/images/help/repository/https-url-clone-cli.png and b/assets/images/help/repository/https-url-clone-cli.png differ
diff --git a/assets/images/help/repository/repository-options-branch.png b/assets/images/help/repository/repository-options-branch.png
index edd292327ef0..6dd4b77af3ec 100644
Binary files a/assets/images/help/repository/repository-options-branch.png and b/assets/images/help/repository/repository-options-branch.png differ
diff --git a/assets/images/help/repository/repository-options-defaultbranch-change.png b/assets/images/help/repository/repository-options-defaultbranch-change.png
index 03fcd0d1f7bb..8fe9624a6997 100644
Binary files a/assets/images/help/repository/repository-options-defaultbranch-change.png and b/assets/images/help/repository/repository-options-defaultbranch-change.png differ
diff --git a/assets/images/help/repository/repository-options-defaultbranch-drop-down.png b/assets/images/help/repository/repository-options-defaultbranch-drop-down.png
index d03ff4b17c14..82600a01712a 100644
Binary files a/assets/images/help/repository/repository-options-defaultbranch-drop-down.png and b/assets/images/help/repository/repository-options-defaultbranch-drop-down.png differ
diff --git a/assets/images/help/repository/repository-options-defaultbranch-i-understand.png b/assets/images/help/repository/repository-options-defaultbranch-i-understand.png
index ee7ba995adee..7f5793f92c99 100644
Binary files a/assets/images/help/repository/repository-options-defaultbranch-i-understand.png and b/assets/images/help/repository/repository-options-defaultbranch-i-understand.png differ
diff --git a/assets/images/help/repository/repository-options-defaultbranch-update.png b/assets/images/help/repository/repository-options-defaultbranch-update.png
index b6c948174ea8..1b2b15f909ce 100644
Binary files a/assets/images/help/repository/repository-options-defaultbranch-update.png and b/assets/images/help/repository/repository-options-defaultbranch-update.png differ
diff --git a/assets/images/help/repository/rerun-checks-drop-down.png b/assets/images/help/repository/rerun-checks-drop-down.png
index e23d91fa477a..3aa271bba265 100644
Binary files a/assets/images/help/repository/rerun-checks-drop-down.png and b/assets/images/help/repository/rerun-checks-drop-down.png differ
diff --git a/assets/images/help/repository/run-name.png b/assets/images/help/repository/run-name.png
index 2f8313adb847..5398fbc6aac9 100644
Binary files a/assets/images/help/repository/run-name.png and b/assets/images/help/repository/run-name.png differ
diff --git a/assets/images/help/repository/super-linter-workflow-results.png b/assets/images/help/repository/super-linter-workflow-results.png
index 2823fd5f7593..fd99dbeb670a 100644
Binary files a/assets/images/help/repository/super-linter-workflow-results.png and b/assets/images/help/repository/super-linter-workflow-results.png differ
diff --git a/assets/images/help/repository/superlinter-lint-code-base-job.png b/assets/images/help/repository/superlinter-lint-code-base-job.png
index 11829cef240a..b24c3c06b7f9 100644
Binary files a/assets/images/help/repository/superlinter-lint-code-base-job.png and b/assets/images/help/repository/superlinter-lint-code-base-job.png differ
diff --git a/assets/images/help/repository/superlinter-run-name.png b/assets/images/help/repository/superlinter-run-name.png
index 7a9413df60e4..7e5fdfd4fdbe 100644
Binary files a/assets/images/help/repository/superlinter-run-name.png and b/assets/images/help/repository/superlinter-run-name.png differ
diff --git a/assets/images/help/repository/superlinter-workflow-sidebar.png b/assets/images/help/repository/superlinter-workflow-sidebar.png
index 0593891c41c1..d120147e0964 100644
Binary files a/assets/images/help/repository/superlinter-workflow-sidebar.png and b/assets/images/help/repository/superlinter-workflow-sidebar.png differ
diff --git a/assets/images/help/repository/view-run-billable-time.png b/assets/images/help/repository/view-run-billable-time.png
index 4f6b38ad9a98..9f1b8643f928 100644
Binary files a/assets/images/help/repository/view-run-billable-time.png and b/assets/images/help/repository/view-run-billable-time.png differ
diff --git a/assets/images/help/repository/workflow-job.png b/assets/images/help/repository/workflow-job.png
index 920e17bde662..65ecd382930a 100644
Binary files a/assets/images/help/repository/workflow-job.png and b/assets/images/help/repository/workflow-job.png differ
diff --git a/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png b/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png
index 117c87659a27..b35c5fa6ab0f 100644
Binary files a/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png and b/assets/images/help/repository/workflow-run-kebab-horizontal-icon.png differ
diff --git a/assets/images/help/repository/workflow-sidebar.png b/assets/images/help/repository/workflow-sidebar.png
index c9421ba6cf3a..4888815882c9 100644
Binary files a/assets/images/help/repository/workflow-sidebar.png and b/assets/images/help/repository/workflow-sidebar.png differ
diff --git a/assets/images/help/settings/settings-sidebar-ssh-keys.png b/assets/images/help/settings/settings-sidebar-ssh-keys.png
index 1ad509a2cf4e..1a52c894b2c8 100644
Binary files a/assets/images/help/settings/settings-sidebar-ssh-keys.png and b/assets/images/help/settings/settings-sidebar-ssh-keys.png differ
diff --git a/assets/images/help/settings/settings-ssh-key-review.png b/assets/images/help/settings/settings-ssh-key-review.png
index 765c760227ac..1c6c5f278336 100644
Binary files a/assets/images/help/settings/settings-ssh-key-review.png and b/assets/images/help/settings/settings-ssh-key-review.png differ
diff --git a/assets/images/help/settings/ssh-sso-authorize.png b/assets/images/help/settings/ssh-sso-authorize.png
index 45fda14956eb..a9bb79aee511 100644
Binary files a/assets/images/help/settings/ssh-sso-authorize.png and b/assets/images/help/settings/ssh-sso-authorize.png differ
diff --git a/assets/images/help/settings/ssh-sso-button.png b/assets/images/help/settings/ssh-sso-button.png
index 61bdbcd4e07d..314c9585a75b 100644
Binary files a/assets/images/help/settings/ssh-sso-button.png and b/assets/images/help/settings/ssh-sso-button.png differ
diff --git a/assets/images/help/settings/userbar-account-settings.png b/assets/images/help/settings/userbar-account-settings.png
index 8594e68400b1..aa4ddfcee842 100644
Binary files a/assets/images/help/settings/userbar-account-settings.png and b/assets/images/help/settings/userbar-account-settings.png differ
diff --git a/assets/images/octocat-books.png b/assets/images/octocat-books.png
index 1586da406746..6ef8e109c76f 100644
Binary files a/assets/images/octocat-books.png and b/assets/images/octocat-books.png differ
diff --git a/content/LICENSE b/content/LICENSE
deleted file mode 100644
index 9238c8f93880..000000000000
--- a/content/LICENSE
+++ /dev/null
@@ -1,386 +0,0 @@
-Attribution 4.0 International
-
-=======================================================================
-
-Creative Commons Corporation ("Creative Commons") is not a law firm and
-does not provide legal services or legal advice. Distribution of
-Creative Commons public licenses does not create a lawyer-client or
-other relationship. Creative Commons makes its licenses and related
-information available on an "as-is" basis. Creative Commons gives no
-warranties regarding its licenses, any material licensed under their
-terms and conditions, or any related information. Creative Commons
-disclaims all liability for damages resulting from their use to the
-fullest extent possible.
-
-Using Creative Commons Public Licenses
-
-Creative Commons public licenses provide a standard set of terms and
-conditions that creators and other rights holders may use to share
-original works of authorship and other material subject to copyright
-and certain other rights specified in the public license below. The
-following considerations are for informational purposes only, are not
-exhaustive, and do not form part of our licenses.
-
- Considerations for licensors: Our public licenses are
- intended for use by those authorized to give the public
- permission to use material in ways otherwise restricted by
- copyright and certain other rights. Our licenses are
- irrevocable. Licensors should read and understand the terms
- and conditions of the license they choose before applying it.
- Licensors should also secure all rights necessary before
- applying our licenses so that the public can reuse the
- material as expected. Licensors should clearly mark any
- material not subject to the license. This includes other CC-
- licensed material, or material used under an exception or
- limitation to copyright. More considerations for licensors:
- wiki.creativecommons.org/Considerations_for_licensors
-
- Considerations for the public: By using one of our public
- licenses, a licensor grants the public permission to use the
- licensed material under specified terms and conditions. If
- the licensor's permission is not necessary for any reason--for
- example, because of any applicable exception or limitation to
- copyright--then that use is not regulated by the license. Our
- licenses grant only permissions under copyright and certain
- other rights that a licensor has authority to grant. Use of
- the licensed material may still be restricted for other
- reasons, including because others have copyright or other
- rights in the material. A licensor may make special requests,
- such as asking that all changes be marked or described.
- Although not required by our licenses, you are encouraged to
- respect those requests where reasonable. More considerations
- for the public:
- wiki.creativecommons.org/Considerations_for_licensees
-
-=======================================================================
-
-Creative Commons Attribution 4.0 International Public License
-
-By exercising the Licensed Rights (defined below), You accept and agree
-to be bound by the terms and conditions of this Creative Commons
-Attribution 4.0 International Public License ("Public License"). To the
-extent this Public License may be interpreted as a contract, You are
-granted the Licensed Rights in consideration of Your acceptance of
-these terms and conditions, and the Licensor grants You such rights in
-consideration of benefits the Licensor receives from making the
-Licensed Material available under these terms and conditions.
-
-Section 1 -- Definitions.
-
- a. Adapted Material means material subject to Copyright and Similar
- Rights that is derived from or based upon the Licensed Material
- and in which the Licensed Material is translated, altered,
- arranged, transformed, or otherwise modified in a manner requiring
- permission under the Copyright and Similar Rights held by the
- Licensor. For purposes of this Public License, where the Licensed
- Material is a musical work, performance, or sound recording,
- Adapted Material is always produced where the Licensed Material is
- synched in timed relation with a moving image.
-
- b. Adapter's License means the license You apply to Your Copyright
- and Similar Rights in Your contributions to Adapted Material in
- accordance with the terms and conditions of this Public License.
-
- c. Copyright and Similar Rights means copyright and/or similar rights
- closely related to copyright including, without limitation,
- performance, broadcast, sound recording, and Sui Generis Database
- Rights, without regard to how the rights are labeled or
- categorized. For purposes of this Public License, the rights
- specified in Section 2(b)(1)-(2) are not Copyright and Similar
- Rights.
-
- d. Effective Technological Measures means those measures that, in the
- absence of proper authority, may not be circumvented under laws
- fulfilling obligations under Article 11 of the WIPO Copyright
- Treaty adopted on December 20, 1996, and/or similar international
- agreements.
-
- e. Exceptions and Limitations means fair use, fair dealing, and/or
- any other exception or limitation to Copyright and Similar Rights
- that applies to Your use of the Licensed Material.
-
- f. Licensed Material means the artistic or literary work, database,
- or other material to which the Licensor applied this Public
- License.
-
- g. Licensed Rights means the rights granted to You subject to the
- terms and conditions of this Public License, which are limited to
- all Copyright and Similar Rights that apply to Your use of the
- Licensed Material and that the Licensor has authority to license.
-
- h. Licensor means the individual(s) or entity(ies) granting rights
- under this Public License.
-
- i. Share means to provide material to the public by any means or
- process that requires permission under the Licensed Rights, such
- as reproduction, public display, public performance, distribution,
- dissemination, communication, or importation, and to make material
- available to the public including in ways that members of the
- public may access the material from a place and at a time
- individually chosen by them.
-
- j. Sui Generis Database Rights means rights other than copyright
- resulting from Directive 96/9/EC of the European Parliament and of
- the Council of 11 March 1996 on the legal protection of databases,
- as amended and/or succeeded, as well as other essentially
- equivalent rights anywhere in the world.
-
- k. You means the individual or entity exercising the Licensed Rights
- under this Public License. Your has a corresponding meaning.
-
-Section 2 -- Scope.
-
- a. License grant.
-
- 1. Subject to the terms and conditions of this Public License,
- the Licensor hereby grants You a worldwide, royalty-free,
- non-sublicensable, non-exclusive, irrevocable license to
- exercise the Licensed Rights in the Licensed Material to:
-
- a. reproduce and Share the Licensed Material, in whole or
- in part; and
-
- b. produce, reproduce, and Share Adapted Material.
-
- 2. Exceptions and Limitations. For the avoidance of doubt, where
- Exceptions and Limitations apply to Your use, this Public
- License does not apply, and You do not need to comply with
- its terms and conditions.
-
- 3. Term. The term of this Public License is specified in Section
- 6(a).
-
- 4. Media and formats; technical modifications allowed. The
- Licensor authorizes You to exercise the Licensed Rights in
- all media and formats whether now known or hereafter created,
- and to make technical modifications necessary to do so. The
- Licensor waives and/or agrees not to assert any right or
- authority to forbid You from making technical modifications
- necessary to exercise the Licensed Rights, including
- technical modifications necessary to circumvent Effective
- Technological Measures. For purposes of this Public License,
- simply making modifications authorized by this Section 2(a)
- (4) never produces Adapted Material.
-
- 5. Downstream recipients.
-
- a. Offer from the Licensor -- Licensed Material. Every
- recipient of the Licensed Material automatically
- receives an offer from the Licensor to exercise the
- Licensed Rights under the terms and conditions of this
- Public License.
-
- b. No downstream restrictions. You may not offer or impose
- any additional or different terms or conditions on, or
- apply any Effective Technological Measures to, the
- Licensed Material if doing so restricts exercise of the
- Licensed Rights by any recipient of the Licensed
- Material.
-
- 6. No endorsement. Nothing in this Public License constitutes or
- may be construed as permission to assert or imply that You
- are, or that Your use of the Licensed Material is, connected
- with, or sponsored, endorsed, or granted official status by,
- the Licensor or others designated to receive attribution as
- provided in Section 3(a)(1)(A)(i).
-
- b. Other rights.
-
- 1. Moral rights, such as the right of integrity, are not
- licensed under this Public License, nor are publicity,
- privacy, and/or other similar personality rights; however, to
- the extent possible, the Licensor waives and/or agrees not to
- assert any such rights held by the Licensor to the limited
- extent necessary to allow You to exercise the Licensed
- Rights, but not otherwise.
-
- 2. Patent and trademark rights are not licensed under this
- Public License.
-
- 3. To the extent possible, the Licensor waives any right to
- collect royalties from You for the exercise of the Licensed
- Rights, whether directly or through a collecting society
- under any voluntary or waivable statutory or compulsory
- licensing scheme. In all other cases the Licensor expressly
- reserves any right to collect such royalties.
-
-Section 3 -- License Conditions.
-
-Your exercise of the Licensed Rights is expressly made subject to the
-following conditions.
-
- a. Attribution.
-
- 1. If You Share the Licensed Material (including in modified
- form), You must:
-
- a. retain the following if it is supplied by the Licensor
- with the Licensed Material:
-
- i. identification of the creator(s) of the Licensed
- Material and any others designated to receive
- attribution, in any reasonable manner requested by
- the Licensor (including by pseudonym if
- designated);
-
- ii. a copyright notice;
-
- iii. a notice that refers to this Public License;
-
- iv. a notice that refers to the disclaimer of
- warranties;
-
- v. a URI or hyperlink to the Licensed Material to the
- extent reasonably practicable;
-
- b. indicate if You modified the Licensed Material and
- retain an indication of any previous modifications; and
-
- c. indicate the Licensed Material is licensed under this
- Public License, and include the text of, or the URI or
- hyperlink to, this Public License.
-
- 2. You may satisfy the conditions in Section 3(a)(1) in any
- reasonable manner based on the medium, means, and context in
- which You Share the Licensed Material. For example, it may be
- reasonable to satisfy the conditions by providing a URI or
- hyperlink to a resource that includes the required
- information.
-
- 3. If requested by the Licensor, You must remove any of the
- information required by Section 3(a)(1)(A) to the extent
- reasonably practicable.
-
- 4. If You Share Adapted Material You produce, the Adapter's
- License You apply must not prevent recipients of the Adapted
- Material from complying with this Public License.
-
-Section 4 -- Sui Generis Database Rights.
-
-Where the Licensed Rights include Sui Generis Database Rights that
-apply to Your use of the Licensed Material:
-
- a. for the avoidance of doubt, Section 2(a)(1) grants You the right
- to extract, reuse, reproduce, and Share all or a substantial
- portion of the contents of the database;
-
- b. if You include all or a substantial portion of the database
- contents in a database in which You have Sui Generis Database
- Rights, then the database in which You have Sui Generis Database
- Rights (but not its individual contents) is Adapted Material; and
-
- c. You must comply with the conditions in Section 3(a) if You Share
- all or a substantial portion of the contents of the database.
-
-For the avoidance of doubt, this Section 4 supplements and does not
-replace Your obligations under this Public License where the Licensed
-Rights include other Copyright and Similar Rights.
-
-Section 5 -- Disclaimer of Warranties and Limitation of Liability.
-
- a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
- EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
- AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
- ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
- IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
- WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
- PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
- ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
- KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
- ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
-
- b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
- TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
- NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
- INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
- COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
- USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
- ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
- DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
- IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
-
- c. The disclaimer of warranties and limitation of liability provided
- above shall be interpreted in a manner that, to the extent
- possible, most closely approximates an absolute disclaimer and
- waiver of all liability.
-
-Section 6 -- Term and Termination.
-
- a. This Public License applies for the term of the Copyright and
- Similar Rights licensed here. However, if You fail to comply with
- this Public License, then Your rights under this Public License
- terminate automatically.
-
- b. Where Your right to use the Licensed Material has terminated under
- Section 6(a), it reinstates:
-
- 1. automatically as of the date the violation is cured, provided
- it is cured within 30 days of Your discovery of the
- violation; or
-
- 2. upon express reinstatement by the Licensor.
-
- For the avoidance of doubt, this Section 6(b) does not affect any
- right the Licensor may have to seek remedies for Your violations
- of this Public License.
-
- c. For the avoidance of doubt, the Licensor may also offer the
- Licensed Material under separate terms or conditions or stop
- distributing the Licensed Material at any time; however, doing so
- will not terminate this Public License.
-
- d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
- License.
-
-Section 7 -- Other Terms and Conditions.
-
- a. The Licensor shall not be bound by any additional or different
- terms or conditions communicated by You unless expressly agreed.
-
- b. Any arrangements, understandings, or agreements regarding the
- Licensed Material not stated herein are separate from and
- independent of the terms and conditions of this Public License.
-
-Section 8 -- Interpretation.
-
- a. For the avoidance of doubt, this Public License does not, and
- shall not be interpreted to, reduce, limit, restrict, or impose
- conditions on any use of the Licensed Material that could lawfully
- be made without permission under this Public License.
-
- b. To the extent possible, if any provision of this Public License is
- deemed unenforceable, it shall be automatically reformed to the
- minimum extent necessary to make it enforceable. If the provision
- cannot be reformed, it shall be severed from this Public License
- without affecting the enforceability of the remaining terms and
- conditions.
-
- c. No term or condition of this Public License will be waived and no
- failure to comply consented to unless expressly agreed to by the
- Licensor.
-
- d. Nothing in this Public License constitutes or may be interpreted
- as a limitation upon, or waiver of, any privileges and immunities
- that apply to the Licensor or You, including from the legal
- processes of any jurisdiction or authority.
-
-=======================================================================
-
-Creative Commons is not a party to its public
-licenses. Notwithstanding, Creative Commons may elect to apply one of
-its public licenses to material it publishes and in those instances
-will be considered the โLicensor.โ The text of the Creative Commons
-public licenses is dedicated to the public domain under the CC0 Public
-Domain Dedication. Except for the limited purpose of indicating that
-material is shared under a Creative Commons public license or as
-otherwise permitted by the Creative Commons policies published at
-creativecommons.org/policies, Creative Commons does not authorize the
-use of the trademark "Creative Commons" or any other trademark or logo
-of Creative Commons without its prior written consent including,
-without limitation, in connection with any unauthorized modifications
-to any of its public licenses or any other arrangements,
-understandings, or agreements concerning use of licensed material. For
-the avoidance of doubt, this paragraph does not form part of the
-public licenses.
-
-Creative Commons may be contacted at creativecommons.org.
diff --git a/content/actions/guides/caching-dependencies-to-speed-up-workflows.md b/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
index 36c25cb0946d..497bcad57e58 100644
--- a/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
+++ b/content/actions/guides/caching-dependencies-to-speed-up-workflows.md
@@ -184,8 +184,8 @@ For example, if a pull request contains a `feature` branch (the current scope) a
1. Key `npm-feature-` in the `feature` branch scope
2. Key `npm-` in the `feature` branch scope
1. Key `npm-feature-d5ea0750` in the `main` branch scope
-3. Key `npm-d5ea0750` in the `main` branch scope
-4. Key `npm` in the `main` branch scope
+3. Key `npm-feature-` in the `main` branch scope
+4. Key `npm-` in the `main` branch scope
### Usage limits and eviction policy
diff --git a/content/actions/guides/storing-workflow-data-as-artifacts.md b/content/actions/guides/storing-workflow-data-as-artifacts.md
index 6da23f063a6d..a069551e1333 100644
--- a/content/actions/guides/storing-workflow-data-as-artifacts.md
+++ b/content/actions/guides/storing-workflow-data-as-artifacts.md
@@ -18,7 +18,9 @@ versions:
### About workflow artifacts
-Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. For pushes and pull requests, {% data variables.product.product_name %} stores artifacts for 90 days. The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
+Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended.
+
+{% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
These are some of the common artifacts that you can upload:
@@ -48,89 +50,6 @@ To share data between jobs:
The steps of a job share the same environment on the runner machine, but run in their own individual processes. To pass data between steps in a job, you can use inputs and outputs. For more information about inputs and outputs, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)."
-### Passing data between jobs in a workflow
-
-You can use the `upload-artifact` and `download-artifact` actions to share data between jobs in a workflow. This example workflow illustrates how to pass data between jobs in the same workflow. For more information, see the {% if currentVersion == "free-pro-team@latest" %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.product.product_location %}{% endif %}.
-
-Jobs that are dependent on a previous job's artifacts must wait for the dependent job to complete successfully. This workflow uses the `needs` keyword to ensure that `job_1`, `job_2`, and `job_3` run sequentially. For example, `job_2` requires `job_1` using the `needs: job_1` syntax.
-
-Job 1 performs these steps:
-- Performs a math calculation and saves the result to a text file called `math-homework.txt`.
-- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the name `homework`. The action places the file in a directory named `homework`.
-
-Job 2 uses the result in the previous job:
-- Downloads the `homework` artifact uploaded in the previous job. By default, the `download-artifact` action downloads artifacts to the workspace directory that the step is executing in. You can use the `path` input parameter to specify a different download directory.
-- Reads the value in the `homework/math-homework.txt` file, performs a math calculation, and saves the result to `math-homework.txt`.
-- Uploads the `math-homework.txt` file. This upload overwrites the previous upload because both of the uploads share the same name.
-
-Job 3 displays the result uploaded in the previous job:
-- Downloads the `homework` artifact.
-- Prints the result of the math equation to the log.
-
-The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`.
-
-```yaml
-name: Share data between jobs
-
-on: [push]
-
-jobs:
- job_1:
- name: Add 3 and 7
- runs-on: ubuntu-latest
- steps:
- - shell: bash
- run: |
- expr 3 + 7 > math-homework.txt
- - name: Upload math result for job 1
- uses: actions/upload-artifact@v2
- with:
- name: homework
- path: math-homework.txt
-
- job_2:
- name: Multiply by 9
- needs: job_1
- runs-on: windows-latest
- steps:
- - name: Download math result for job 1
- uses: actions/download-artifact@v2
- with:
- name: homework
- - shell: bash
- run: |
- value=`cat math-homework.txt`
- expr $value \* 9 > math-homework.txt
- - name: Upload math result for job 2
- uses: actions/upload-artifact@v2
- with:
- name: homework
- path: math-homework.txt
-
- job_3:
- name: Display results
- needs: job_2
- runs-on: macOS-latest
- steps:
- - name: Download math result for job 2
- uses: actions/download-artifact@v2
- with:
- name: homework
- - name: Print the final result
- shell: bash
- run: |
- value=`cat math-homework.txt`
- echo The result is $value
-```
-
-![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png)
-
-### Sharing data between workflow runs
-
-After a workflow ends, you can download a compressed file of the uploaded artifacts on {% data variables.product.product_name %} by finding the workflow run in the **Actions** tab. You can also use the {% data variables.product.prodname_dotcom %} REST API to download artifacts. For more information, see "[Artifacts](/v3/actions/artifacts/)."
-
-If you need to access artifacts from a previous workflow run, you can use the {% data variables.product.product_name %} REST API to retrieve artifacts. For more information, see "[Get an artifact](/rest/reference/actions#artifacts)."
-
### Uploading build and test artifacts
You can create a continuous integration (CI) workflow to build and test your code. For more information about using {% data variables.product.prodname_actions %} to perform CI, see "[About continuous integration](/articles/about-continuous-integration)."
@@ -191,13 +110,32 @@ jobs:
![Image of workflow upload artifact workflow run](/assets/images/help/repository/upload-build-test-artifact.png)
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+### Configuring a custom artifact retention period
+
+You can define a custom retention period for individual artifacts created by a workflow. When using a workflow to create a new artifact, you can use `retention-days` with the `upload-artifact` action. This example demonstrates how to set a custom retention period of 5 days for the artifact named `my-artifact`:
+
+```
+ - name: 'Upload Artifact'
+ uses: actions/upload-artifact@v2
+ with:
+ name: my-artifact
+ path: my_file.txt
+ retention-days: 5
+```
+
+The `retention-days` value cannot exceed the retention limit set by the repository, organization, or enterprise.
+{% endif %}
+
### Downloading or deleting artifacts
-During a workflow run, you can download artifacts that were previously uploaded in the same workflow run. After a workflow run has been completed, you can download or delete artifacts on GitHub using the workflow run history.
+During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact)action to download artifacts that were previously uploaded in the same workflow run.
+
+After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/v3/actions/artifacts/)."
#### Downloading artifacts during a workflow run
-The [actions/download-artifact](https://github.com/actions/download-artifact) action can be used to download previously uploaded artifacts during a workflow run.
+The [`actions/download-artifact`](https://github.com/actions/download-artifact) action can be used to download previously uploaded artifacts during a workflow run.
{% note %}
@@ -225,24 +163,82 @@ If you download all a workflow run's artifacts, a directory for each artifact is
For more information on syntax, see the {% if currentVersion == "free-pro-team@latest" %}[actions/download-artifact](https://github.com/actions/download-artifact) action{% else %} `actions/download-artifact` action on {% data variables.product.product_location %}{% endif %}.
-#### Downloading and deleting artifacts after a workflow run is complete
+### Passing data between jobs in a workflow
+
+You can use the `upload-artifact` and `download-artifact` actions to share data between jobs in a workflow. This example workflow illustrates how to pass data between jobs in the same workflow. For more information, see the {% if currentVersion == "free-pro-team@latest" %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.product.product_location %}{% endif %}.
+
+Jobs that are dependent on a previous job's artifacts must wait for the dependent job to complete successfully. This workflow uses the `needs` keyword to ensure that `job_1`, `job_2`, and `job_3` run sequentially. For example, `job_2` requires `job_1` using the `needs: job_1` syntax.
+
+Job 1 performs these steps:
+- Performs a math calculation and saves the result to a text file called `math-homework.txt`.
+- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the name `homework`. The action places the file in a directory named `homework`.
+
+Job 2 uses the result in the previous job:
+- Downloads the `homework` artifact uploaded in the previous job. By default, the `download-artifact` action downloads artifacts to the workspace directory that the step is executing in. You can use the `path` input parameter to specify a different download directory.
+- Reads the value in the `homework/math-homework.txt` file, performs a math calculation, and saves the result to `math-homework.txt`.
+- Uploads the `math-homework.txt` file. This upload overwrites the previous upload because both of the uploads share the same name.
+
+Job 3 displays the result uploaded in the previous job:
+- Downloads the `homework` artifact.
+- Prints the result of the math equation to the log.
+
+The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`.
+
+```yaml
+name: Share data between jobs
-Artifacts automatically expire after 90 days, but you can always reclaim used {% data variables.product.prodname_actions %} storage by deleting artifacts before they expire on {% data variables.product.product_name %}.
+on: [push]
-{% warning %}
+jobs:
+ job_1:
+ name: Add 3 and 7
+ runs-on: ubuntu-latest
+ steps:
+ - shell: bash
+ run: |
+ expr 3 + 7 > math-homework.txt
+ - name: Upload math result for job 1
+ uses: actions/upload-artifact@v2
+ with:
+ name: homework
+ path: math-homework.txt
-**Warning:** Once you delete an artifact, it can not be restored.
+ job_2:
+ name: Multiply by 9
+ needs: job_1
+ runs-on: windows-latest
+ steps:
+ - name: Download math result for job 1
+ uses: actions/download-artifact@v2
+ with:
+ name: homework
+ - shell: bash
+ run: |
+ value=`cat math-homework.txt`
+ expr $value \* 9 > math-homework.txt
+ - name: Upload math result for job 2
+ uses: actions/upload-artifact@v2
+ with:
+ name: homework
+ path: math-homework.txt
-{% endwarning %}
+ job_3:
+ name: Display results
+ needs: job_2
+ runs-on: macOS-latest
+ steps:
+ - name: Download math result for job 2
+ uses: actions/download-artifact@v2
+ with:
+ name: homework
+ - name: Print the final result
+ shell: bash
+ run: |
+ value=`cat math-homework.txt`
+ echo The result is $value
+```
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.actions-tab %}
-{% data reusables.repositories.navigate-to-workflow %}
-{% data reusables.repositories.view-run %}
-1. To download artifacts, use the **Artifacts** drop-down menu, and select the artifact you want to download.
- ![Download artifact drop-down menu](/assets/images/help/repository/artifact-drop-down.png)
-1. To delete artifacts, use the **Artifacts** drop-down menu, and click {% octicon "trashcan" aria-label="The trashcan icon" %}.
- ![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact.png)
+![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png)
{% if currentVersion == "free-pro-team@latest" %}
diff --git a/content/actions/learn-github-actions/index.md b/content/actions/learn-github-actions/index.md
index 9329c5bac2e2..8bc97d038f8e 100644
--- a/content/actions/learn-github-actions/index.md
+++ b/content/actions/learn-github-actions/index.md
@@ -37,5 +37,6 @@ versions:
{% link_with_intro /sharing-workflows-with-your-organization %}
{% link_with_intro /security-hardening-for-github-actions %}
{% link_with_intro /migrating-from-circleci-to-github-actions %}
+{% link_with_intro /migrating-from-gitlab-cicd-to-github-actions %}
{% link_with_intro /migrating-from-azure-pipelines-to-github-actions %}
{% link_with_intro /migrating-from-jenkins-to-github-actions %}
diff --git a/content/actions/learn-github-actions/managing-complex-workflows.md b/content/actions/learn-github-actions/managing-complex-workflows.md
index 5c9601e87ad9..38e7e68e94cd 100644
--- a/content/actions/learn-github-actions/managing-complex-workflows.md
+++ b/content/actions/learn-github-actions/managing-complex-workflows.md
@@ -20,6 +20,7 @@ If your workflows use sensitive data, such as passwords or certificates, you can
This example action demonstrates how to reference an existing secret as an environment variable, and send it as a parameter to an example command.
+{% raw %}
```yaml
jobs:
example-job:
@@ -30,6 +31,7 @@ jobs:
run: |
example-command "$SUPER_SECRET"
```
+{% endraw %}
For more information, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
@@ -62,6 +64,7 @@ For more information, see [`jobs..needs`](/actions/reference/workflow-sy
You can use a build matrix if you want your workflow to run tests across multiple combinations of operating systems, platforms, and languages. The build matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this build matrix will run the job multiple times, using different versions of Node.js:
+{% raw %}
```yaml
jobs:
build:
@@ -74,6 +77,7 @@ jobs:
with:
node-version: ${{ matrix.node }}
```
+{% endraw %}
For more information, see [`jobs..strategy.matrix`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
@@ -83,6 +87,7 @@ For more information, see [`jobs..strategy.matrix`](/actions/reference/w
This example demonstrates how to cache the ` ~/.npm` directory:
+{% raw %}
```yaml
jobs:
example-job:
@@ -97,6 +102,7 @@ jobs:
restore-keys: |
${{ runner.os }}-build-${{ env.cache-name }}-
```
+{% endraw %}
For more information, see "[Caching dependencies to speed up workflows](/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows)."
diff --git a/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
new file mode 100644
index 000000000000..873144e8fe04
--- /dev/null
+++ b/content/actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
@@ -0,0 +1,476 @@
+---
+title: Migrating from GitLab CI/CD to GitHub Actions
+intro: '{% data variables.product.prodname_actions %} and GitLab CI/CD share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.'
+versions:
+ free-pro-team: '*'
+ enterprise-server: '>=2.22'
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+### Introduction
+
+GitLab CI/CD and {% data variables.product.prodname_actions %} both allow you to create workflows that automatically build, test, publish, release, and deploy code. GitLab CI/CD and {% data variables.product.prodname_actions %} share some similarities in workflow configuration:
+
+- Workflow configuration files are written in YAML and are stored in the code's repository.
+- Workflows include one or more jobs.
+- Jobs include one or more steps or individual commands.
+- Jobs can run on either managed or self-hosted machines.
+
+There are a few differences, and this guide will show you the important differences so that you can migrate your workflow to {% data variables.product.prodname_actions %}.
+
+### Jobs
+
+Jobs in GitLab CI/CD are very similar to jobs in {% data variables.product.prodname_actions %}. In both systems, jobs have the following characteristics:
+
+* Jobs contain a series of steps or scripts that run sequentially.
+* Jobs can run on separate machines or in separate containers.
+* Jobs run in parallel by default, but can be configured to run sequentially.
+
+You can run a script or a shell command in a job. In GitLab CI/CD, script steps are specified using the `script` key. In {% data variables.product.prodname_actions %}, all scripts are specified using the `run` key.
+
+Below is an example of the syntax for each system:
+
+
+
+
+GitLab CI/CD
+ |
+
+{% data variables.product.prodname_actions %}
+ |
+
+
+
+{% raw %}
+```yaml
+job1:
+ variables:
+ GIT_CHECKOUT: "true"
+ script:
+ - echo "Run your script here"
+```
+{% endraw %}
+ |
+
+{% raw %}
+```yaml
+jobs:
+ job1:
+ steps:
+ - uses: actions/checkout@v2
+ - run: echo "Run your script here"
+```
+{% endraw %}
+ |
+
+
+
+### Runners
+
+Runners are machines on which the jobs run. Both GitLab CI/CD and {% data variables.product.prodname_actions %} offer managed and self-hosted variants of runners. In GitLab CI/CD, `tags` are used to run jobs on different platforms, while in {% data variables.product.prodname_actions %} it is done with the `runs-on` key.
+
+Below is an example of the syntax for each system:
+
+
+
+
+GitLab CI/CD
+ |
+
+{% data variables.product.prodname_actions %}
+ |
+
+
+
+{% raw %}
+```yaml
+windows_job:
+ tags:
+ - windows
+ script:
+ - echo Hello, %USERNAME%!
+
+linux_job:
+ tags:
+ - linux
+ script:
+ - echo "Hello, $USER!"
+```
+{% endraw %}
+ |
+
+{% raw %}
+```yaml
+windows_job:
+ runs-on : windows-latest
+ steps:
+ - run: echo Hello, %USERNAME%!
+
+linux_job:
+ runs-on: ubuntu-latest
+ steps:
+ - run: echo "Hello, $USER!"
+```
+{% endraw %}
+ |
+
+
+
+For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+
+### Docker images
+
+Both GitLab CI/CD and {% data variables.product.prodname_actions %} support running jobs in a Docker image. In GitLab CI/CD, Docker images are defined with a `image` key, while in {% data variables.product.prodname_actions %} it is done with the `container` key.
+
+Below is an example of the syntax for each system:
+
+
+
+
+GitLab CI/CD
+ |
+
+{% data variables.product.prodname_actions %}
+ |
+
+
+
+{% raw %}
+```yaml
+my_job:
+ image: node:10.16-jessie
+```
+{% endraw %}
+ |
+
+{% raw %}
+```yaml
+jobs:
+ my_job:
+ container: node:10.16-jessie
+```
+{% endraw %}
+ |
+
+
+
+For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer)."
+
+### Condition and expression syntax
+
+GitLab CI/CD uses `rules` to determine if a job will run for a specific condition. {% data variables.product.prodname_actions %} uses the `if` keyword to prevent a job from running unless a condition is met.
+
+Below is an example of the syntax for each system:
+
+
+
+
+GitLab CI/CD
+ |
+
+{% data variables.product.prodname_actions %}
+ |
+
+
+
+{% raw %}
+```yaml
+deploy_prod:
+ stage: deploy
+ script:
+ - echo "Deply to production server"
+ rules:
+ - if: '$CI_COMMIT_BRANCH == "master"'
+```
+{% endraw %}
+ |
+
+{% raw %}
+```yaml
+jobs:
+ deploy_prod:
+ if: contains( github.ref, 'master')
+ runs-on: ubuntu-latest
+ steps:
+ - run: echo "Deply to production server"
+```
+{% endraw %}
+ |
+
+
+
+For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)."
+
+### Dependencies between Jobs
+
+Both GitLab CI/CD and {% data variables.product.prodname_actions %} allow you to set dependencies for a job. In both systems, jobs run in parallel by default, but job dependencies in {% data variables.product.prodname_actions %} can be specified explicitly with the `needs` key. GitLab CI/CD also has a concept of `stages`, where jobs in a stage run concurrently, but the next stage will start when all the jobs in the previous stage have completed. You can recreate this scenario in {% data variables.product.prodname_actions %} with the `needs` key.
+
+Below is an example of the syntax for each system. The workflows start with two jobs named `build_a` and `build_b` running in parallel, and when those jobs complete, another job called `test_ab` will run. Finally, when `test_ab` completes, the `deploy_ab` job will run.
+
+
+
+
+GitLab CI/CD
+ |
+
+{% data variables.product.prodname_actions %}
+ |
+
+
+
+{% raw %}
+```yaml
+stages:
+ - build
+ - test
+ - deploy
+
+build_a:
+ stage: build
+ script:
+ - echo "This job will run first."
+
+build_b:
+ stage: build
+ script:
+ - echo "This job will run first, in parallel with build_a."
+
+test_ab:
+ stage: test
+ script:
+ - echo "This job will run after build_a and build_b have finished."
+
+deploy_ab:
+ stage: deploy
+ script:
+ - echo "This job will run after test_ab is complete"
+```
+{% endraw %}
+ |
+
+{% raw %}
+```yaml
+jobs:
+ build_a:
+ runs-on: ubuntu-latest
+ steps:
+ - run: echo "This job will be run first."
+
+ build_b:
+ runs-on: ubuntu-latest
+ steps:
+ - run: echo "This job will be run first, in parallel with build_a"
+
+ test_ab:
+ runs-on: ubuntu-latest
+ needs: [build_a,build_b]
+ steps:
+ - run: echo "This job will run after build_a and build_b have finished"
+
+ deploy_ab:
+ runs-on: ubuntu-latest
+ needs: [test_ab]
+ steps:
+ - run: echo "This job will run after test_ab is complete"
+```
+{% endraw %}
+ |
+
+
+
+For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+
+### Scheduling workflows
+
+Both GitLab CI/CD and {% data variables.product.prodname_actions %} allow you to run workflows at a specific interval. In GitLab CI/CD, pipeline schedules are configured with the UI, while in {% data variables.product.prodname_actions %} you can trigger a workflow on a scheduled interval with the "on" key.
+
+For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#scheduled-events)."
+
+### Variables and secrets
+
+GitLab CI/CD and {% data variables.product.prodname_actions %} support setting environment variables in the pipeline or workflow configuration file, and creating secrets using the GitLab or {% data variables.product.product_name %} UI.
+
+For more information, see "[Environment variables](/actions/reference/environment-variables)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+
+### Caching
+
+GitLab CI/CD and {% data variables.product.prodname_actions %} provide a method in the configuration file to manually cache workflow files.
+
+Below is an example of the syntax for each system:
+
+
+
+
+GitLab CI/CD
+ |
+
+{% data variables.product.prodname_actions %}
+ |
+
+
+
+{% raw %}
+```yaml
+image: node:latest
+
+cache:
+ key: $CI_COMMIT_REF_SLUG
+ paths:
+ - .npm/
+
+before_script:
+ - npm ci --cache .npm --prefer-offline
+
+test_async:
+ script:
+ - node ./specs/start.js ./specs/async.spec.js
+```
+{% endraw %}
+ |
+
+{% raw %}
+```yaml
+jobs:
+ test_async:
+ - name: Cache node modules
+ uses: actions/cache@v2
+ with:
+ path: ~/.npm
+ key: v1-npm-deps-${{ hashFiles('**/package-lock.json') }}
+ restore-keys: v1-npm-deps-
+```
+{% endraw %}
+ |
+
+
+
+For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)."
+
+### Artifacts
+
+Both GitLab CI/CD and {% data variables.product.prodname_actions %} can upload files and directories created by a job as artifacts. In {% data variables.product.prodname_actions %}, artifacts can be used to persist data across multiple jobs.
+
+Below is an example of the syntax for each system:
+
+
+
+
+GitLab CI/CD
+ |
+
+{% data variables.product.prodname_actions %}
+ |
+
+
+
+{% raw %}
+```yaml
+script:
+artifacts:
+ paths:
+ - math-homework.txt
+```
+{% endraw %}
+ |
+
+{% raw %}
+```yaml
+- name: Upload math result for job 1
+ uses: actions/upload-artifact@v2
+ with:
+ name: homework
+ path: math-homework.txt
+```
+{% endraw %}
+ |
+
+
+
+For more information, see "[Storing workflow data as artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
+
+### Databases and service containers
+
+Both systems enable you to include additional containers for databases, caching, or other dependencies.
+
+In GitLab CI/CD, a container for the job is specified with the `image` key, while {% data variables.product.prodname_actions %} uses the `container` key. In both systems, additional service containers are specified with the `services` key.
+
+Below is an example of the syntax for each system:
+
+
+
+
+GitLab CI/CD
+ |
+
+{% data variables.product.prodname_actions %}
+ |
+
+
+
+{% raw %}
+```yaml
+container-job:
+ variables:
+ POSTGRES_PASSWORD: postgres
+ # The hostname used to communicate with the
+ # PostgreSQL service container
+ POSTGRES_HOST: postgres
+ # The default PostgreSQL port
+ POSTGRES_PORT: 5432
+ image: node:10.18-jessie
+ services:
+ - postgres
+ script:
+ # Performs a clean installation of all dependencies
+ # in the `package.json` file
+ - npm ci
+ # Runs a script that creates a PostgreSQL client,
+ # populates the client with data, and retrieves data
+ - node client.js
+ tags:
+ - docker
+```
+{% endraw %}
+ |
+
+{% raw %}
+```yaml
+jobs:
+ container-job:
+ runs-on: ubuntu-latest
+ container: node:10.18-jessie
+
+ services:
+ postgres:
+ image: postgres
+ env:
+ POSTGRES_PASSWORD: postgres
+
+ steps:
+ - name: Check out repository code
+ uses: actions/checkout@v2
+
+ # Performs a clean installation of all dependencies
+ # in the `package.json` file
+ - name: Install dependencies
+ run: npm ci
+
+ - name: Connect to PostgreSQL
+ # Runs a script that creates a PostgreSQL client,
+ # populates the client with data, and retrieves data
+ run: node client.js
+ env:
+ # The hostname used to communicate with the
+ # PostgreSQL service container
+ POSTGRES_HOST: postgres
+ # The default PostgreSQL port
+ POSTGRES_PORT: 5432
+```
+{% endraw %}
+ |
+
+
+
+For more information, see "[About service containers](/actions/guides/about-service-containers)."
diff --git a/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md b/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md
index 167b74d4aa42..d7c662b90dba 100644
--- a/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md
+++ b/content/actions/learn-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -33,7 +33,7 @@ For more information, see "[Core concepts for {% data variables.product.prodname
Jenkins lets you send builds to a single build agent, or you can distribute them across multiple agents. You can also classify these agents according to various attributes, such as operating system types.
-Similiarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. The following table compares how the distributed build concept is implemented for both Jenkins and {% data variables.product.prodname_actions %}.
+Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. The following table compares how the distributed build concept is implemented for both Jenkins and {% data variables.product.prodname_actions %}.
| Jenkins | {% data variables.product.prodname_actions %} |
| ------------- | ------------- |
@@ -41,7 +41,7 @@ Similiarly, {% data variables.product.prodname_actions %} can send jobs to {% da
#### Using sections to organize pipelines
-Jenkins splits its Declarative Pipelines into multiple sections. Similiarly, {% data variables.product.prodname_actions %} organizes its workflows into separate sections. The table below compares Jenkins sections with the {% data variables.product.prodname_actions %} workflow.
+Jenkins splits its Declarative Pipelines into multiple sections. Similarly, {% data variables.product.prodname_actions %} organizes its workflows into separate sections. The table below compares Jenkins sections with the {% data variables.product.prodname_actions %} workflow.
|Jenkins Directives | {% data variables.product.prodname_actions %} |
| ------------- | ------------- |
diff --git a/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
index 5b64e0af0d8e..22d5651efe6e 100644
--- a/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
+++ b/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -1,6 +1,6 @@
---
title: Downloading workflow artifacts
-intro: You can download artifacts that were archived during a workflow run. Artifacts automatically expire after 90 days.
+intro: You can download archived artifacts before they automatically expire.
product: '{% data reusables.gated-features.actions %}'
versions:
free-pro-team: '*'
@@ -10,6 +10,9 @@ versions:
{% data reusables.actions.enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. For more information, see "[Configuring the retention period for GitHub Actions artifacts and logs in your repository](/github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %}
+{% if currentVersion == "enterprise-server@2.22" %} {% data variables.product.product_name %} stores full build logs and artifacts for 90 days.{% endif %}
+
{% data reusables.repositories.permissions-statement-read %}
{% data reusables.repositories.navigate-to-repo %}
diff --git a/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
index c0ed87a4b83a..32eb4e4cbba2 100644
--- a/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
+++ b/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -1,6 +1,6 @@
---
title: Removing workflow artifacts
-intro: 'Artifacts automatically expire after 90 days, but you can always reclaim used {% data variables.product.prodname_actions %} storage by deleting artifacts before they expire on {% data variables.product.product_name %}.'
+intro: 'You can reclaim used {% data variables.product.prodname_actions %} storage by deleting artifacts before they expire on {% data variables.product.product_name %}.'
product: '{% data reusables.gated-features.actions %}'
versions:
free-pro-team: '*'
@@ -10,6 +10,8 @@ versions:
{% data reusables.actions.enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}
+### Deleting an artifact
+
{% warning %}
**Warning:** Once you delete an artifact, it can not be restored.
@@ -18,9 +20,23 @@ versions:
{% data reusables.repositories.permissions-statement-write %}
+{% data reusables.github-actions.artifact-log-retention-statement %}
+
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.actions-tab %}
{% data reusables.repositories.navigate-to-workflow %}
{% data reusables.repositories.view-run %}
1. Under **Artifacts**, click {% octicon "trashcan" aria-label="The trashcan icon" %} next to the artifact you want to remove.
![Delete artifact drop-down menu](/assets/images/help/repository/actions-delete-artifact.png)
+
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
+### Setting the retention period for an artifact
+
+Retention periods for artifacts and logs can be configured at the repository, organization, and enterprise level. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."
+
+You can also define a custom retention period for individual artifacts using the `actions/upload-artifact` action in a workflow. For more information, see "[Storing workflow data as artifacts](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period)."
+
+### Finding the expiration date of an artifact
+
+You can use the API to confirm the date that an artifact is scheduled to be deleted. For more information, see the `expires_at` value returned by "[List artifacts for a repository](/rest/reference/actions#artifacts)."
+{% endif %}
\ No newline at end of file
diff --git a/content/actions/managing-workflow-runs/using-workflow-run-logs.md b/content/actions/managing-workflow-runs/using-workflow-run-logs.md
index 70bbe0b7ad59..34a54f88694b 100644
--- a/content/actions/managing-workflow-runs/using-workflow-run-logs.md
+++ b/content/actions/managing-workflow-runs/using-workflow-run-logs.md
@@ -1,6 +1,6 @@
---
title: Using workflow run logs
-intro: 'You can view, search, and download the logs for each job in a workflow run. {% data variables.product.product_name %} stores full build logs and artifacts for 90 days.'
+intro: 'You can view, search, and download the logs for each job in a workflow run.'
product: '{% data reusables.gated-features.actions %}'
versions:
free-pro-team: '*'
diff --git a/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/content/actions/reference/context-and-expression-syntax-for-github-actions.md
index a33f7f34e6ca..8c86fb1bb5f5 100644
--- a/content/actions/reference/context-and-expression-syntax-for-github-actions.md
+++ b/content/actions/reference/context-and-expression-syntax-for-github-actions.md
@@ -84,24 +84,24 @@ The `github` context contains information about the workflow run and the event t
| Property name | Type | Description |
|---------------|------|-------------|
| `github` | `object` | The top-level context available during any job or step in a workflow. |
+| `github.action` | `string` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number. For example, the first script you run will have the name `run1`, and the second script will be named `run2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
+| `github.action_path` | `string` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite run steps actions. |
+| `github.actor` | `string` | The login of the user that initiated the workflow run. |
+| `github.base_ref` | `string` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is a `pull_request`. |
| `github.event` | `object` | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context. |
+| `github.event_name` | `string` | The name of the event that triggered the workflow run. |
| `github.event_path` | `string` | The path to the full event webhook payload on the runner. |
-| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
+| `github.head_ref` | `string` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is a `pull_request`. |
| `github.job` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. |
-| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
-| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
-| `github.actor` | `string` | The login of the user that initiated the workflow run. |
+| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. |
| `github.repository` | `string` | The owner and repository name. For example, `Codertocat/Hello-World`. |
| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
-| `github.event_name` | `string` | The name of the event that triggered the workflow run. |
+| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
+| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
| `github.sha` | `string` | The commit SHA that triggered the workflow run. |
-| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. |
-| `github.head_ref` | `string` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is a `pull_request`. |
-| `github.base_ref` | `string` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is a `pull_request`. |
| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." |
+| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
| `github.workspace` | `string` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
-| `github.action` | `string` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number. For example, the first script you run will have the name `run1`, and the second script will be named `run2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
-| `github.action_path` | `string` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite run steps actions.
#### **`env` context**
@@ -124,14 +124,14 @@ The `job` context contains information about the currently running job.
| Property name | Type | Description |
|---------------|------|-------------|
| `job` | `object` | This context changes for each job in a workflow run. You can access this context from any step in a job. |
-| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. |
| `job.container` | `object` | Information about the job's container. For more information about containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)." |
-| `job.container.network` | `string` | The id of the container network. The runner creates the network used by all containers in a job. |
| `job.container.id` | `string` | The id of the container. |
+| `job.container.network` | `string` | The id of the container network. The runner creates the network used by all containers in a job. |
| `job.services` | `object` | The service containers created for a job. For more information about service containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)." |
| `job.services..id` | `string` | The id of the service container. |
-| `job.services..ports` | `object` | The exposed ports of the service container. |
| `job.services..network` | `string` | The id of the service container network. The runner creates the network used by all containers in a job. |
+| `job.services..ports` | `object` | The exposed ports of the service container. |
+| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. |
#### **`steps` context**
@@ -141,9 +141,9 @@ The `steps` context contains information about the steps in the current job that
|---------------|------|-------------|
| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
| `steps..outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." |
-| `steps..outputs.