Caution
If you upgrade to v1.1.5+, please remember to:
- move the GIST ID to the Secret
- move the TIMEZONE to the Repository variable For details, refer to the third point in Project Setup.
p.s. when you see this notice in the README of your forked repository, it means you have upgraded to v1.1.5
Are you an early 🐤 or a night 🦉?
When are you most productive during the day?
Let's check out in gist!
This project is inspired by an awesome pinned-gist project.
Find more in https://github.com/matchai/awesome-pinned-gists
This project uses GitHub graphQL API to get the commit histories and write into the gist by rest.js
- Create a new public GitHub Gist (https://gist.github.com/)
- Create a token with the
gist
andrepo
scope and copy it. (https://github.com/settings/tokens/new)enable
repo
scope seems DANGEROUS
but this GitHub Action only accesses your commit timestamp in the repositories you contributed.
-
Fork this repo
-
Open the "Actions" tab of your fork and click the "enable" button
-
Go to the repo Settings > Secrets and variables > Actions, add the following secrets / variables:
Type Name Description Repository Secrets GH_TOKEN The GitHub token generated above. Repository Secrets GIST_ID The ID portion from your gist URL, e.g., 9842e074b8ee46aef76fd0d493bae0ed
.Repository Variable TIMEZONE The timezone of your location, e.g., Asia/Taipei
for Taiwan,America/New_York
for America in New York, etc.Below is the final screenshot: (Click the image for a clearer view.)
Repository Secret Repository Variable -
Manually run the workflow for the first time or wait for the scheduled run. (The workflow will run every day at 00:00 UTC.)
- Go to the "Actions" tab on your fork
- Select the "Update gist" workflow
- Click the "Run workflow" button