yoshi389111/git-turf

The git-turf program outputs ASCII art to GitHub contribution graph

🚀 My Projects

• GitHub Actions
  • yoshi389111/github-profile-3d-contrib - Create a 3D GitHub Contribution Calendar.
• VS Code extensions (marketplace)
  • yoshi389111/vscode-md-table-rainbow - Color each column of the markdown table.
  • yoshi389111/visible-whitespace - Make whitespace visible.
• Command line tools
  • yoshi389111/pong-is-not-ping - POng is Not pinG
  • yoshi389111/power-hello - Create SVG images of powerful keystrokes.
  • yoshi389111/git-turf - Outputs ASCII art to the GitHub contribution graph.
  • yoshi389111/git-caesar - Encrypt/decrypt files passwordlessly using GitHub's public key.
• Tech blog: dev.to

🗾 My Projects (Japanease only)

• yoshi389111/kinokobooks - 「きのこ本」を勝手に電子書籍化
• yoshi389111/dq1pswd - ふっかつのじゅもんを作れます。１の方です。
• yoshi389111/dq2pswd - ふっかつのじゅもんを作れます。２の方です。
• Tech blog: Qiita / Zenn

📝 Misc

• LGTM collections

git-turf's Issues

Thank you and a little suggestion on docs

Thank you for sharing your great work and fun ideas! I like your way of documentation, examples, especially the copyright/license notice. I wonder if you can add more to the docs, such as the following.

• preconditions
  • does the calendar have to be blank?
  • does it depend on a certain version of GitHub environment?
• side effects
  • does running this app clear the existing calendar?
• idempotence
  • what happens if it's run twice with different input?

I know I can get the answers from reading the source code, and all should do that before they run any scripts downloaded from the internet. But there is a difference between the current behavior and your design goals.

Cheers,
lqu