actions/create-pull-request
1
0
Fork 0
mirror of https://forgejo.stefka.eu/jiriks74/create-pull-request.git synced 2025-01-18 16:01:06 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: update action versions

Browse source
This commit is contained in:
Peter Evans 2022-03-22 17:09:01 +09:00
parent 62892adaf4
commit 6dc3ed9086
3 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -192,7 +192,7 @@ To create a project card for the pull request, pass the `pull-request-number` st
- name: Create or Update Project Card - name: Create or Update Project Card
if: ${{ steps.cpr.outputs.pull-request-number }} if: ${{ steps.cpr.outputs.pull-request-number }}
uses: peter-evans/create-or-update-project-card@v1 uses: peter-evans/create-or-update-project-card@v2
with: with:
project-name: My project project-name: My project
column-name: My column column-name: My column

4
docs/concepts-guidelines.md
View file

@ -36,7 +36,7 @@ For each [event type](https://docs.github.com/en/actions/reference/events-that-t
The default can be overridden by specifying a `ref` on checkout. The default can be overridden by specifying a `ref` on checkout.
```yml ```yml
- uses: actions/checkout@v2 - uses: actions/checkout@v3
with: with:
ref: develop ref: develop
``` ```
@ -73,7 +73,7 @@ jobs:
example: example:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- uses: actions/checkout@v2 - uses: actions/checkout@v3
``` ```
There may be use cases where it makes sense to execute the workflow on a branch that is not the base of the pull request. In these cases, the base branch can be specified with the `base` action input. The action will attempt to rebase changes made during the workflow on to the actual base. There may be use cases where it makes sense to execute the workflow on a branch that is not the base of the pull request. In these cases, the base branch can be specified with the `base` action input. The action will attempt to rebase changes made during the workflow on to the actual base.

12
docs/examples.md
View file

@ -146,9 +146,9 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- uses: actions/checkout@v3 - uses: actions/checkout@v3
- uses: actions/setup-node@v2 - uses: actions/setup-node@v3
with: with:
node-version: '12.x' node-version: '16.x'
- name: Update dependencies - name: Update dependencies
run: | run: |
npx -p npm-check-updates ncu -u npx -p npm-check-updates ncu -u
@ -182,9 +182,9 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- uses: actions/checkout@v3 - uses: actions/checkout@v3
- uses: actions/setup-node@v2 - uses: actions/setup-node@v3
with: with:
node-version: 12.x node-version: 16.x
- run: npm ci - run: npm ci
- run: npm run test - run: npm run test
- run: npm run build - run: npm run build
@ -428,7 +428,7 @@ An `on: repository_dispatch` workflow can be triggered from another workflow wit
```yml ```yml
- name: Repository Dispatch - name: Repository Dispatch
uses: peter-evans/repository-dispatch@v1 uses: peter-evans/repository-dispatch@v2
with: with:
token: ${{ secrets.REPO_ACCESS_TOKEN }} token: ${{ secrets.REPO_ACCESS_TOKEN }}
repository: username/my-repo repository: username/my-repo
@ -574,7 +574,7 @@ The template is rendered using the [render-template](https://github.com/chuhlomi
```yml ```yml
- name: Render template - name: Render template
id: template id: template
uses: chuhlomin/render-template@v1.2 uses: chuhlomin/render-template@v1.4
with: with:
template: .github/pull-request-template.md template: .github/pull-request-template.md
vars: | vars: |