Merge branch 'main' into codespaces-devcontainer-update

Author: saritai

.github/PULL_REQUEST_TEMPLATE.md

@@ -14,7 +14,7 @@ Thanks again!
 
 Closes [issue link]
 
-<!-- 
+<!--
 - If there's an existing issue for your change, please link to it.
 - If there's _not_ an existing issue, please open one first to make it more likely that this update will be accepted: https://github.com/github/docs/issues/new/choose. -->
 
@@ -24,8 +24,8 @@ Closes [issue link]
 
 ### Check off the following:
 
-- [ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click **View deployment**).
-- [ ] For content changes, I have completed the [self-review checklist](https://github.com/github/docs/blob/main/contributing/self-review.md#self-review).
+- [ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click **Modified** to view your latest changes).
+- [ ] For content changes, I have completed the [self-review checklist](https://github.com/github/docs/blob/main/CONTRIBUTING.md#self-review).
 
 ### Writer impact (This section is for GitHub staff members only):
 

.github/actions-scripts/enterprise-server-issue-templates/deprecation-issue.md

@@ -70,3 +70,8 @@ You may need to include the changes in step 6 to get tests to pass.
     - [ ] Debug any test failures or unexpected results. 
 - [ ] When the PR is approved, merge it in to complete the deprecation. This can be merged independently from step 5. 
 
+## Step 7: Deprecate the OpenAPI description in `github/github`
+    
+- [ ] In `github/github`, edit the release's config file in `app/api/description/config/releases/`, and change `deprecated: false` to `deprecated: true`.
+- [ ] Open a new PR, and get the required code owner approvals. A docs-content team member can approve it for the docs team.
+- [ ] When the PR is approved, merge the `github/github` PR.

.github/dependabot.yml

@@ -3,7 +3,7 @@ updates:
   - package-ecosystem: npm
     directory: '/'
     schedule:
-      interval: weekly
+      interval: monthly
     open-pull-requests-limit: 20 # default is 5
 
   - package-ecosystem: 'github-actions'

.github/workflows/staging-build-pr.yml

@@ -96,6 +96,14 @@ jobs:
       - name: Set npm script for Heroku build to noop
         run: npm set-script heroku-postbuild "echo 'Application was pre-built!'"
 
+      - name: Delete heavy things we won't need deployed
+        run: |
+          # Non-WIP translations we don't support yet.
+          rm -fr translations/de* translations/ru* translations/ko* translations/ru*
+
+          # Not needed to run after having been built.
+          rm -fr .next/cache
+
       - name: Create an archive
         run: |
           tar -c --file=app.tar \
@@ -116,11 +124,15 @@ jobs:
             app.json \
             Procfile
 
+          ls -lh app.tar
+          zstd -q app.tar -o app.tar.zst
+          ls -lh app.tar.zst
+
       # Upload only the files needed to run this application.
       # We are not willing to trust the rest (e.g. script/) for the remainder
       # of the deployment process.
       - name: Upload build artifact
         uses: actions/upload-artifact@27121b0bdffd731efa15d66772be8dc71245d074
         with:
           name: pr_build
-          path: app.tar
+          path: app.tar.zst

.github/workflows/staging-deploy-pr.yml

@@ -325,6 +325,7 @@ jobs:
 
       - name: Extract user-changes to temp directory
         run: |
+          zstd -d -q $RUNNER_TEMP/app.tar.zst -o $RUNNER_TEMP/app.tar
           mkdir $RUNNER_TEMP/app
           tar -x --file=$RUNNER_TEMP/app.tar -C "$RUNNER_TEMP/app/"
 

.gitignore

@@ -15,3 +15,4 @@ coverage/
 blc_output.log
 blc_output_internal.log
 broken_links.md
+lib/redirects/.redirects-cache_*.json

CONTRIBUTING.md

@@ -32,7 +32,7 @@ If you spot a problem with the docs, [search if an issue already exists](https:/
 
 #### Solve an issue
 
-Scan through our [existing issues](https://github.com/github/docs/issues) to find one that interests you. You can narrow down the search using `labels` as filters. See [Labels](/contributing/how-to-use-labels.md) for more information.
+Scan through our [existing issues](https://github.com/github/docs/issues) to find one that interests you. You can narrow down the search using `labels` as filters. See [Labels](/contributing/how-to-use-labels.md) for more information. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.
 
 ### Make Changes