Automate the crawling and cataloging of the Tailwind UI components

1. Create a private GitHub repository.

2. Add TAILWINDUI_EMAIL and TAILWINDUI_PASSWORD secrets to the GitHub repository.

3. Optionally create a .env file with additional settings for the crawler.

4. Create a new file .github/workflows/default.yml:

   name: Update
   on:
     workflow_dispatch: # On manual trigger
     schedule:
       - cron: "0 0 * * *" # Every day at midnight
   
   jobs:
     update:
       name: Update
       runs-on: ubuntu-latest
       steps:
         - name: Checkout
           uses: actions/checkout@v2
         - name: Run crawler
           uses: gregbrimble/tailwindui-crawler-action@v1.1.0
           with:
             email: ${{ secrets.TAILWINDUI_EMAIL }}
             password: ${{ secrets.TAILWINDUI_PASSWORD }}

   Read more about the schedule cron syntax in the official GitHub Actions documentation.

A live example can be found in .github/workflows/default.yml.

To be emailed whenever there is a change to a component, simply setup GitHub Notifications on your repository.

The following input options are available:

Note: If using a separate private repository for the output, you must include a Personal Access Token in the token input, as the {{ github.token }} tokens are scoped to only the current repository.