kevin/neovim
1
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2024-12-19 18:55:14 -07:00
Code Issues Packages Projects Releases Wiki Activity

ci(backport): remove triggering by comment (#18210)

Browse Source 
Triggering by comment is not needed. Applying the label is enough to
trigger the backport action.
This commit is contained in:
zeertzjq 2022-04-24 05:26:42 +08:00 committed by GitHub
parent d3df415228
commit cfaf7440fc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.github/workflows/backport.yml vendored
View File

@ -2,8 +2,6 @@ name: Backport
on: on:
pull_request_target: pull_request_target:
types: [closed, labeled] types: [closed, labeled]
issue_comment:
types: [created]
jobs: jobs:
backport: backport:
permissions: permissions:
@ -14,10 +12,6 @@ jobs:
github.repository_owner == 'neovim' && ( github.repository_owner == 'neovim' && (
github.event_name == 'pull_request_target' && github.event_name == 'pull_request_target' &&
github.event.pull_request.merged github.event.pull_request.merged
) || (
github.event_name == 'issue_comment' &&
github.event.issue.pull_request &&
contains(github.event.comment.body, '/backport')
) )
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:

7
MAINTAIN.md
View File

@ -57,11 +57,8 @@ has a major bug:
The neovim repository includes a backport [github action](https://github.com/zeebe-io/backport-action). The neovim repository includes a backport [github action](https://github.com/zeebe-io/backport-action).
In order to trigger the action, a PR must be labeled with a label matching the In order to trigger the action, a PR must be labeled with a label matching the
form `backport release-0.X`. If the label is applied before the PR is merged, form `backport release-0.X`. Note, the PR must have a description in the issue body,
the backport will be filed automatically against the target branch. Otherwise, or the backport will fail.
comment `\backport` on the merged PR *after* the label has been applied to trigger
a backport. Note, the PR must have a description in the issue body, or the backport
will fail.
Third-party dependencies Third-party dependencies
-------------- --------------