📊 Weekly development breakdown

📊 Weekly development breakdown

TypeScript  21 hrs 47 mins  ████████████████▒░░░  67.1%
Vue.js       6 hrs 21 mins  ██████▓░░░░░░░░░░░░░  19.6%
JSON         2 hrs 10 mins  ████▒░░░░░░░░░░░░░░░   6.7%
JavaScript         46 mins  ███▒░░░░░░░░░░░░░░░░   2.4%

What's the file type for the gist?

Nothing, just plain text

Have some issues here. After I triggered the action, the file within the gist was deleted, and the title of it turned to gist:<:id>. Triggered the action again, and the console output:

Unable to update gist
HttpError: Validation Failed: {"resource":"Gist","code":"missing_field","field":"files"}

Additional info:
Already has data in the Wakatime Dashboard.
Already checked all profile setting https://wakatime.com/settings/profile.

Maybe I should wait a couple of days to ensure the Wakatime has enough data?

It works now, just needs to be patient haha.

如果根据 matchai/waka-box 的 README.md 没能成功实现，可以按照接下来的操作，

• matchai/waka-box 定义的计划任务频率：每天零点执行一次。所以别期望推送代码后就能看到最终效果；
• 修改 fork 后项目内的 schedule.yml 配置；

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 }}

• 有需要，可以调整计划任务频率，如：每两小时执行一次。这个操作并非必须的。注意，Github Actions 支持的最小频率是：每 5 分钟；

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 }}

做完这些就没问题了，到时间就可以看到效果。

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.