wip / action Goto Github PK

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Hello,

The action is failing on npm ci run.

2020-10-25T11:19:06.1790805Z npm notice 
2020-10-25T11:19:06.1791266Z npm notice New patch version of npm available! 7.0.3 -> 7.0.5
2020-10-25T11:19:06.1791901Z npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.0.5>
2020-10-25T11:19:06.1792502Z npm notice Run `npm install -g [email protected]` to update!
2020-10-25T11:19:06.1792845Z npm notice 
2020-10-25T11:19:06.1799788Z npm ERR! The `npm ci` command can only install with an existing package-lock.json or
2020-10-25T11:19:06.1800615Z npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
2020-10-25T11:19:06.1801376Z npm ERR! later to generate a package-lock.json file, then try again.
2020-10-25T11:19:06.1884172Z npm ERR! A complete log of this run can be found in:
2020-10-25T11:19:06.1885100Z npm ERR!     /root/.npm/_logs/2020-10-25T11_19_06_180Z-debug.log
2020-10-25T11:19:06.3839692Z The command '/bin/sh -c npm ci --only=production' returned a non-zero code: 1
2020-10-25T11:19:06.3864834Z ##[warning]Docker build failed with exit code 1, back off 3.163 seconds before retry.

Anything i can do to fix it on my end?

TIA,
Eli

I'm trying to get this Github Action workflow to work and can't figure it out.
What I've tried:
"WIP", "wip" in pull request titles.
"wip" in branch name.
Please let me know what I'm doing wrong.

"WIP (action) Pending — work in progress" stays like this forever. Details link points to the https://github.com/wip/action.

README says

An example workflow looks like this (switch to the <> Edit new file tab when creating a new workflow and paste the code below):

I feel stupid asking this but what is "<> Edit new file tab when creating a new workflow"?
I've saved this PR as:

cat .github/workflows/wip_pr_label.yml                                                                                                                              master  ✱
name: WIP
on:
  pull_request:
    types: [ opened, synchronize, reopened, edited ]

jobs:
  wip:
    runs-on: ubuntu-latest
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    steps:
      - uses: wip/[email protected]

I have a project that employs this action.
For some reason I cannot figure out, WIP is always blocking my PRs without any apparent reason (to me at least).

For example this PR:
crim-ca/weaver#244

As shown in the below image, all my tests are passing, I got all mandatory branch protection approvals, etc.
The only thing that blocks my PR is the "incomplete" WIP action check, which has requirement of WIP (action) defined in branch protection as per the README of this repo.

It is configured here: https://github.com/crim-ca/weaver/blob/wip-action/.github/workflows/pr-labeler.yml

Any idea of what might be at cause of this issue?
Thanks!

Added this in a pull request, though the action produces this:

Run wip/action@master
/usr/bin/docker run --name ee64e760ebf75cc4ca4bcb05716d63461be_77fac4 --label 671ee6 --workdir /github/workspace --rm -e INPUT_GITHUB_TOKEN -e HOME -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e GITHUB_ACTIONS=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/hungerrush-docs/hungerrush-docs":"/github/workspace" 671ee6:4e760ebf75cc4ca4bcb05716d63461be
There are environment variables missing from this runtime, but would be present on GitHub.
- GITHUB_TOKEN
(node:1) UnhandledPromiseRejectionWarning: HttpError: Bad credentials
    at /node_modules/@octokit/request/lib/request.js:55:27
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The action I've defined looks like this:

on: [pull_request]
name: "Set status on pull_request"

jobs:
  wip:
    name: "Set status"
    runs-on: ubuntu-latest
    steps:
      - uses: wip/action@master
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}

It would be nice if you could also check for the "wip" and "work in progress" labels when determining if a PR is in WIP status.

Having tried to implement this action, we found first that the example had incorrect indentation, and once corrected produced errors.

our working config:

name: Set PR review status
on:
  pull_request:
    types: [ opened, synchronize, reopened, edited ]

jobs:
  wip:
    name: Set WIP status
    runs-on: ubuntu-latest
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    steps:
      - uses: wip/[email protected]

Would be great to see this on https://github.com/marketplace/actions :)

GitHub recently started showing the following message:
"Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: wip/action"

I believe we should update it as well.