Skip to content

Commit f4f250e

Browse files
committed
Finish blog. Update resume.
1 parent 273b6b4 commit f4f250e

File tree

2 files changed

+21
-3
lines changed

2 files changed

+21
-3
lines changed

_data/resume.json

+18
Original file line numberDiff line numberDiff line change
@@ -289,6 +289,24 @@
289289
}
290290
]
291291
},
292+
{
293+
"name": "github-paint",
294+
"icon": "🎨",
295+
"tags": [
296+
"python",
297+
"github action"
298+
],
299+
"description": [
300+
"A GitHub Action to draw text in your GitHub profile's contributions graph."
301+
],
302+
"links": [
303+
{
304+
"icon": "🖥️",
305+
"text": "github",
306+
"url": "https://github.com/tbrockman/github-paint"
307+
}
308+
]
309+
},
292310
{
293311
"name": "auxb0x",
294312
"icon": "🎵",

_posts/2024-06-28-github-paint.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Since my contribution graph usually looks like this:
1616
![a picture of a pretty empty contribution graph](/assets/img/github-paint/theos-usual-contribution-graph.png)
1717
_< tumbleweed emoji >_
1818

19-
\.\.\.I've always had it in the back of my mind as something I'd like to take a stab at. Primarily for the sake of solving an interesting problem, but also to fuck with recruiters who believe contribution activity strongly correlates with programming ability (*said with chip on shoulder as someone required to use a separate GitHub account for work*).
19+
\.\.\.I've always had it in the back of my mind as something I'd like to take a stab at. Primarily for the sake of solving an interesting problem, but also to mess with recruiters who seem to believe contribution activity strongly correlates with programming ability (*said with chip on shoulder as someone required to use a separate GitHub account for work*).
2020

2121
Since taking a burnout-induced leave-of-absence, I've had some time to explore the problem, which has led to the creation of\.\.\.
2222

@@ -40,6 +40,6 @@ The whole thing is a Python [Typer-CLI](https://typer.tiangolo.com/) that primar
4040
1. Then, after initializing a fresh `git` repository, for each day (in the appropriate chronological order\-\-though this doesn't seem to matter much to GitHub), we forge the necessary number of commits on each date (since `git` allows setting arbitrary commit timestamps).
4141
1. Finally, push the new repository and history (deleting the old one if it exists), and wait a bit for GitHub to render our shiny new contribution graph.
4242

43-
So far, it seems to work pretty well, but it's not *super* battle-tested. if you run into issues feel free to create a pull request: [https://github.com/tbrockman/github-paint](https://github.com/tbrockman/github-paint).
43+
So far, it seems to work pretty well, but it's not *super* battle-tested. if you run into issues feel free to create a pull request in the repository: [https://github.com/tbrockman/github-paint](https://github.com/tbrockman/github-paint).
4444

45-
hope you like it!
45+
✌️

0 commit comments

Comments
 (0)