question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not working on GitHub Actions?

See original GitHub issue

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

When running npx bundlesize in a GitHub Action, I get this warning:

WARN github token not found

You are missing out on some cool features. Read more here: https://github.com/siddharthkp/bundlesize#2-build-status

If the current behavior is a bug, please provide the steps to reproduce.

See output log at See https://github.com/octokit/rest.js/runs/230268601#step:6:6

Configuration:

https://github.com/octokit/rest.js/blob/7e7319208b77cf83eb4c6335c03325befc38901f/.github/workflows/bundlesize.yml#L15-L17

I first had BUNDLESIZE_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} but then changed it to BUNDLESIZE_GITHUB_TOKEN: ${{ secrets.BUNDLESIZE_GITHUB_TOKEN }} with the token provided via the OAuth app.

What is the expected behavior?

It should just work ™️

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information.

  • node version: 12.10.0
  • npm version: version distributed with Node 12.10.0
  • Operating system: Ubuntu latest
  • bundlesize version: latest, run via npx
  • CI you are using: GitHub Actions

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:2
  • Comments:14 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
gr2mcommented, Jun 23, 2020

on: push will not work for pull requests coming from forks

Basically you have to make it work without requiring a GitHub token, as repository secrets are not passed to pull requests from forks

3reactions
patconcommented, Jun 23, 2020

Not sure why, and I think this is still a bug, but I think the simplest resolution here is to use on: push instead of on: pull_request – it will still show up as a status check on PRs.

Broken pull_request: https://github.com/octokit/rest.js/actions/runs/12676607/workflow Working push: https://github.com/redux-saga/redux-saga/pull/1952/files

I did some testing with GitHub Actions, and changing the trigger event was the exact place where it broke in many specific tests.

Read more comments on GitHub >

github_iconTop Results From Across the Web

GitHub Action workflow not running - Stack Overflow
Whenever you add a new workflow, sometimes it may happen that workflow may not get into the running phase even after everything is...
Read more >
My GitHub Actions workflows are not starting - Robs blog
The workflow might have been disabled. On forks all workflows get disabled and you need to manually enabled them (makes sense of course)....
Read more >
Troubleshooting GitHub Actions for your enterprise
Stuck jobs and GitHub Actions memory and CPU limits · 1. Check the overall CPU and memory usage in the management console ·...
Read more >
Github Action Not Showing · Discussion #26479 · community
I am trying to create an action that publishes to pypi when a release is created. I am not seeing the action show...
Read more >
Issues - GitHub
GitHub Actions do not work/run when the .github/workflows/checks.yml file is created in a commit which creates several files at once #642.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found