This monorepo contains all the code necessary to stand up a What The Commit clone. It is built using Serverless Stack and deployed with Seed. I started this project to learn more about the SST API construct when commitment and whatthecommit was down.
Endopoint | Description | Try it | Response |
---|---|---|---|
/ |
Returns a random commit message in txt form. | timmoc.dev | Wubbalubbadubdub! |
/{id} |
Returns the commit message for the {id} . The {id} is the sha256 hash of the actual commit message. |
timmoc.dev/636f571...c357bdf | Wubbalubbadubdub! |
/json |
Returns a random commit message in json form. The key is a sha256 sum of the message. | timmoc.dev/json | {"636f571...c357bdf":"Wubbalubbadubdub!"} |
/json/{id} |
Returns the commit message in json format, including the id , quote , and a json_permalink . The example response is shortened for brevity. |
timmoc.dev/{id} | {"id":"636f571...c357bdf","quote":"Wubbalubbadubdub!","json_permalink":"https://timmoc.dev/json/636f571...c357bdf"} |
For a list of quotes, see quotes.txt or the hashedQuotes json version
I have an alias in my .gitconfig that allows me to run git yolo
and it will commit with a random commit message from this repo. If I feel really adventurous, I can run git yeet
and it will add all the files, commit them, and push.
You can add this git alias and be up and running quickly.
git config --global alias.timmoc '!git commit -m "$(curl -s https://timmoc.dev)"'
Then just run git timmoc
to add a random commit message to your staged changes.
Since most of my projects are solo ventures, I dislike spending time and creative juices creating commit messages that I may never see again. I would rather git yeet
my changes and see them reflected on my development SST stage so I can iterate rapidly. Inspiration to care a little less about personal project commit messages came from this Pieter Levels tweet
Want to see your commit message added to the list? Submit a PR with your commit message added to the quotes.txt file. If you want to add a new feature, please open an issue first.
Github issues are used to track the roadmap. See Roadmap.
Thanks to all the people who donate their time to the SST Discord community and the SST Project. Much of the code in this repo is based on the work of the SST community, commitment, and Nick Gerakines's awesome work.
See my awful commit history
See LICENSE