📊 Weekly development breakdown

Weekly Development

TypeScript   6 hrs 42 mins  ███████████████████▓  83.9%
Markdown        1 hr 1 min  █████▒░░░░░░░░░░░░░░  12.8%
Bash                8 mins  ███▒░░░░░░░░░░░░░░░░   1.9%
JSON                2 mins  ███░░░░░░░░░░░░░░░░░   0.5%

Project address: https://github.com/xrkffgg/waka-box

If you have any question, you can comment below. 😉

What's the file type for the gist ?

What's the file type for the gist ?

plain text

If it fails to be implemented according to matchai/waka-box README.md, it can be implemented according to the following operations.

• Defined scheduled task frequency in matchai/waka-box: once every day at 0: 00. So don't expect to see the final effect after pushing the code;
• Modify the schedule.yml configuration in the project after fork

name: Update gist with WakaTime stats
on: 
  schedule:    
    - cron: "0 0 * * *"
jobs:  
  update-gist: 
    runs-on: ubuntu-latest
    steps: 
      - uses: actions/checkout@master      
      - name: Update gist        
-       uses: matchai/waka-box@master 
+       run: node ./dist/index.js
        env:           
           GH_TOKEN: ${{ secrets.GH_TOKEN }} 
           GIST_ID: 968220c97e8da1d047a9a480fa432e54 
           WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}

• If necessary, you can adjust the frequency of scheduled tasks, for example, once every two hours. This operation is not necessary, the minimum frequency is: every 5 minutes;

name: Update gist with WakaTime stats
on: 
  schedule:    
- - cron: "0 0 * * *"
+ - cron: "0 */2 * * *"
jobs:  
  update-gist: 
    runs-on: ubuntu-latest
    steps: 
      - uses: actions/checkout@master      
      - name: Update gist        
           run: node ./dist/index.js
        env:           
           GH_TOKEN: ${{ secrets.GH_TOKEN }} 
           GIST_ID: 968220c97e8da1d047a9a480fa432e54 
           WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}

When you finish these, there will be no problem, and you will see the effect in time.

@iTonyYo THX