Automate updates with GitHub Actions
See original GitHub issueCurrently the repository is updated by a script that runs locally on @paulirish’s machine. We’d like to move this to a GitHub Actions cronjob workflow. This involves…
- Removing the dependency on a local chromium/src checkout: #265
- Removing the dependency on
yarn
: #267 (not strictly required, but simplifies things) - Automating the
npm publish
process via GitHub Actions (instead of requiring on locale machine configs): #268 - Adding a new workflow to automate daily updates: #271
Issue Analytics
- State:
- Created a year ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Auto Update · Actions · GitHub Marketplace
autoupdate is a GitHub Action that auto-updates pull requests branches whenever changes land on their destination branch.
Read more >Automating Dependency Updates with GitHub Actions
Automating Dependency Updates with GitHub Actions · Step 1: Go to GitHub's marketplace and search for WhiteSource or Renovate. Then, click on Renovate...
Read more >Automating a COVID19 report update and publishing with ...
Github Actions is a fairly recent feature from GitHub which allows you to automate workflows, such as testing code or package deployment.
Read more >Automate development tasks by using GitHub Actions - Training
Create a container action and have it run in a workflow triggered by a push event to your GitHub repository. Save. Prerequisites. A...
Read more >Automating a software company with GitHub Actions - PostHog
This is where GitHub Actions come in. With Actions, you can define per-repository workflows which run on robust runner virtual machines.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
An upstream CDP change just landed: https://chromium-review.googlesource.com/c/chromium/src/+/3749625 This allowed us to test the actual processing logic through the GitHub Actions workflow for the first time. After a few more tweaks (6d6d51eb93edc54a0d015e59f220a2e9ad9f333, 99db35730cedf76819489b2635a6efa9b08becf8, 6870df846388eeb05bf9c85bc9650f9c56501dfc, and 5cde7486078960bfd85083075c305040985dbef9) we just had our first successful, actually-updating-something run! https://github.com/ChromeDevTools/devtools-protocol/runs/7277823196?check_suite_focus=true#step:3:5 It correctly created the Git tag which correctly triggered the
npm publish
-on-tag workflow: https://github.com/ChromeDevTools/devtools-protocol/actions/runs/2647956072 and published tonpm
:After some intense GitHub Actions debugging by creating a temporary workflow and repeatedly force-pushing to
master
like some amateur, I found the root cause. You’re not gonna believe how simple the fix is: a7636c94522c07cf4626dcd64b8993618d0f7192