Merge pull request #429 from peter-evans/dev

v3

.github/workflows/ci.yml

@@ -22,12 +22,10 @@ jobs:
         with:
           python-version: '3.x'
       - run: npm ci
-      - run: npm run clean
       - run: npm run build
       - run: npm run format-check
       - run: npm run lint
       - run: npm run test
-      - run: npm run package
       - uses: actions/upload-artifact@v2
         with:
           name: dist

docs/concepts-guidelines.md

@@ -16,7 +16,7 @@ This document covers terminology, how the action works, general usage guidelines
   - [Push using SSH (deploy keys)](#push-using-ssh-deploy-keys)
   - [Push pull request branches to a fork](#push-pull-request-branches-to-a-fork)
   - [Authenticating with GitHub App generated tokens](#authenticating-with-github-app-generated-tokens)
-  - [Running in a container](#running-in-a-container)
+  - [Running in a container or on self-hosted runners](#running-in-a-container-or-on-self-hosted-runners)
   - [Creating pull requests on tag push](#creating-pull-requests-on-tag-push)
 
 ## Terminology
@@ -253,13 +253,13 @@ GitHub App generated tokens are more secure than using a PAT because GitHub App
           token: ${{ steps.generate-token.outputs.token }}
 ```
 
-### Running in a container
+### Running in a container or on self-hosted runners
 
-This action can be run inside a container by installing the action's dependencies either in the Docker image itself, or during the workflow.
+This action can be run inside a container, or on [self-hosted runners](https://docs.github.com/en/actions/hosting-your-own-runners), by installing the necessary dependencies.
 
-The action requires `git` to be installed and on the `PATH`.
+This action requires `git` to be installed and on the `PATH`. Note that `actions/checkout` requires Git 2.18 or higher to be installed, otherwise it will just download the source of the repository instead of cloning it.
 
-Note that `actions/checkout` requires Git 2.18 or higher to be installed, otherwise it will just download the source of the repository instead of cloning it.
+The following examples of running in a container show the dependencies being installed during the workflow, but they could also be pre-installed in a custom image.
 
 **Alpine container example:**
 ```yml

docs/updating.md

@@ -33,9 +33,9 @@
 
 ### New features
 
-- The action has been converted to Typescript and is much faster than `v2`.
+- The action has been converted to Typescript giving it a significant performance improvement.
 
-- If you run this action in a container, `python` and `pip` are no longer required dependencies. See [Running in a container](concepts-guidelines.md#running-in-a-container) for details.
+- If you run this action in a container, or on [self-hosted runners](https://docs.github.com/en/actions/hosting-your-own-runners), `python` and `pip` are no longer required dependencies. See [Running in a container or on self-hosted runners](concepts-guidelines.md#running-in-a-container-or-on-self-hosted-runners) for details.
 
 - Inputs `labels`, `assignees`, `reviewers` and `team-reviewers` can now be newline separated, or comma separated.
   e.g.

package.json

@@ -5,17 +5,13 @@
   "description": "Creates a pull request for changes to your repository in the actions workspace",
   "main": "lib/main.js",
   "scripts": {
-    "clean": "echo Temporarily kept for backwards compatibility",
     "build": "tsc && ncc build",
     "format": "prettier --write '**/*.ts'",
     "format-check": "prettier --check '**/*.ts'",
     "lint": "eslint src/**/*.ts",
     "test:unit": "jest unit",
     "test:int": "__test__/integration-tests.sh",
-    "test": "npm run test:unit && npm run test:int",
-    "pack-assets": "echo Temporarily kept for backwards compatibility",
-    "vendor-deps": "echo Temporarily kept for backwards compatibility",
-    "package": "echo Temporarily kept for backwards compatibility"
+    "test": "npm run test:unit && npm run test:int"
   },
   "repository": {
     "type": "git",