@todor That's right, you can't point to a specific branch, unfortunately. You could fork the theme, hook up your test blog to the fork, and then send everything upstream when you're happy with your changes. I find the test blog most useful for testing out quick ideas and small changes. When doing extensive theme or plug-in development, I usually work offline with `hugo` on my own machine.

💾 Micro.bloggers (Cc: @help), what is your workflow for testing Micro.blog theme changes with a test blog and a Github repo? I thought of playing with the test blog on a branch and using main for “production”. But I don’t think I can point the test blog to a repo branch via the Micro.blog UI 🤔

2023-12-28 10:07 am

|

Embed

In reply to

sod

@todor That's right, you can't point to a specific branch, unfortunately. You could fork the theme, hook up your test blog to the fork, and then send everything upstream when you're happy with your changes.

I find the test blog most useful for testing out quick ideas and small changes. When doing extensive theme or plug-in development, I usually work offline with hugo on my own machine.

2023-12-28 10:56 am

|

Embed

todor

@sod Thanks for the advice! I'll most likely do the fork approach, seems like a smaller initial investment than setting up the local environment. Though the latter would certainly be the end game!

2023-12-28 11:43 am

|

Embed