Skip to content

Commit 0f6b1f9

Browse files
chore: clean up obsolete scripts and drafts
Signed-off-by: Tsung-Ju Lii <[email protected]>
1 parent e02fba8 commit 0f6b1f9

6 files changed

+1
-164
lines changed

Makefile

-11
This file was deleted.

drafts/cpp-tips-and-gotchas.markdown

-87
This file was deleted.

drafts/templates/listenings.md.j2

-7
This file was deleted.

posts/2025-02-27-make-new-post-via-github-pull-request.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create New Posts by Making Pull Requests
33
layout: post
44
comments: false
5-
tags: about this site
5+
tags: about this blog
66
---
77

88
This is a little easier than I thought it would be. So basically it generates a post from a pull request's body and commits it to branch. I already have an action that reruns the site generator whenever something new appears in directory, so in effect I just need to write whatever I want to write in the PR's body, and press when I'm happy with it.
@@ -13,4 +13,3 @@ More specifically there are 4 GitHub actions in action (no pun intended):
1313
2. Generates the new post file in directory: when I'm good with the PR body and merge the PR, an action will pipe the body into the new file. The draft iteme will also be removed.
1414
3. Run the Haskell site generator. The action detects if anything's changed in , and if so generates the static site. The generator itself doesn't change much, the action nicely takes care of caching it so that it doesn't spend twenty minutes compiling hakyll.
1515
4. Deploy to GH pages. I didn't write this myself.
16-

scripts/generate_year_end_list.py

-35
This file was deleted.

scripts/make_post.py

-22
This file was deleted.

0 commit comments

Comments
 (0)