Skip to content

style: tweak publishing-setup and improve /commit flow #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bhavanaeh merged 2 commits into from
Apr 24, 2026
Merged

style: tweak publishing-setup and improve /commit flow #37

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c4310f5
style: tweak publishing-setup tags and heading
bhavanaeh Apr 24, 2026
adece66
chore: check for merged PR before committing on stale branch
bhavanaeh Apr 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions .claude/commands/commit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
Commit changes in the b-log repo. This command must be run from the repo clone directory.

1. **Check branch**: If the current branch is `v4`, create a feature branch before committing:
- Derive a short branch name from the staged changes (e.g., `feat/add-post-title`, `fix/broken-link`)
- Run `git checkout -b <branch-name>`
1. **Check branch**:
- If the current branch is `v4`, create a feature branch before committing.
- If the current branch already has a merged PR (check with `gh pr list --head <branch> --state merged`), stash changes, checkout `v4`, pull, create a new feature branch, and pop the stash.
- Derive a short branch name from the staged changes (e.g., `feat/add-post-title`, `fix/broken-link`).

2. **Review changes**: Run `git status` and `git diff` to see what's changed. Also check `git log --oneline -5` for recent commit style.

Expand Down
4 changes: 2 additions & 2 deletions quartz/content/publishing-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: publishing setup
date: 2026-04-23
draft: false
tags: [meta, workflow]
tags: [workflow]
---

obsidian for writing, quartz4 for building, github actions for deploying. notes live in `b-log/quartz/content/`, pushes to `v4` trigger a deploy.
Expand All @@ -13,7 +13,7 @@ obsidian for writing, quartz4 for building, github actions for deploying. notes
2. write and iterate
3. run `/publish <note-name>` in claude code when ready

### custom claude code commands i set up
### i set up the following commands (to start with)

`/publish` — the main one. sets `draft: false` in frontmatter, creates a `publish/<note-slug>` branch off `v4`, commits with conventional commit format (`feat: publish <title>`), opens a PR to `v4`, merges it, cleans up.

Expand Down