c2corg / browserslist-update-action Goto Github PK

I use yarn in my project so that would be useful, happy to make a PR to add this.

For monorepo setups one has to run this action in a sub-directory, and not the root. Adding an input for that would be very helpful.

Very much appreciate this action; I've been adding it to many of my org's repos since I found out about it.

Is there any way to specify the version of Node this action should use? I have a project that can't yet be migrated to Node 16 and the npm install fails in this action.
Thanks!

When trying to create a PR, the action is failing with:

adding reviewers to the PR
Error: Request failed due to following response errors:
 - Could not resolve to a node with the global id of 'MatthewMaclean'

The PR is created, but no reviewers are added. My action looks like:

name: Update Browserslist database

on:
 schedule:
   # Every 1st and 15th day of the month at noon UTC
   - cron: '0 12 1,15 * *'

permissions:
 contents: write
 pull-requests: write

jobs:
 update-browserslist-database:
   runs-on: ubuntu-latest
   steps:
     - name: Checkout repository
       uses: actions/checkout@v3
       with:
         fetch-depth: 0
     - name: Configure git
       run: |
         git config --global user.email "[email protected]"
         git config --global user.name "GitHub Action"
     - name: Update Browserslist database and create PR if applies
       uses: c2corg/browserslist-update-action@0e432e6c50c3c06fcb785a3ba475d462dd93272e
       timeout-minutes: 15
       with:
         github_token: ${{ secrets.GITHUB_TOKEN }}
         branch: browserslist-update
         base_branch: main
         commit_message: 'Chore: Update Browserslist db'
         title: 'Chore: Update Browserslist db'
         body: Auto-generated. See https://github.com/browserslist/update-db#why-you-need-to-call-it-regularly
         labels: 'github-action'
         reviewers: 'MatthewMaclean'

Is it possibly an issue with using GITHUB_TOKEN and I need to use a PAT instead? Interested if someone else has this working.

Thanks for amazing project. I added it to Browserslist docs.

Right now, browserslist --update-db prints how DB update changed target browser (to explain why it is important to update DB).

Am I right that PR text is static? Can we add diff code section with the data from browserslist --update-db?

Should we add cron triggers to README.md example?

I think the best strategy is to run tool every 3-5 month.

Feature Request

It can be a nice addition to this action if the created/updated PR number is outputted so that it can be used in other actions.