> I’m new to build.yml files and a bit confused on how to do it. If I 
> understand correctly, this means that everytime I push, the whole blog, 
> including 20years of assets, is gzipped and sent to the host. Isn’t that 
> a bit overkill? Should I care? I not too far from the 1Go limitation but 
> I’m confident that I could optimize some old pictures to reduce the size 
> of the whole blog (which is not far from the 1million words mark).

You might struggle, maybe due to the tar.gz file size, but also because 
of the time taken to uncompress so many files. It's hard to tell unless 
you give it a go.

> ## Both gemini and web?
> 
> The same git repository (which I also host on sr.ht) should serve for 

---
 go.mod | 2 +-
 go.sum | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/go.mod b/go.mod
index 248fa26..59932f4 100644
--- a/go.mod
+++ b/go.mod
@@ -3,6 +3,6 @@ module nova
 go 1.16
 
 require (
-	git.sr.ht/~adnano/go-gemini v0.2.1
[message trimmed]

And just to put a bow on it, a re-test of the private repo with private
tracker with both now referenced in a private project worked too.

Ian

Oops, no, this repo and traker didn't have a project (it does now). 🤦

I just did another test with the repo that I previously used and that
already has a project, and it worked, thanks!

Cheers,

Ian

Hey Adnan,

I just gave it a go, pushing to a `develop` branch on a private repo, it
didn't close the referenced ticket in the private tracker.

Just in case the feature only works for the default branch, I then
merged `develop` into `master` locally and pushed to sr.ht. This too did
not result in the ticket getting closed. 🤷

Am I doing something wrong?

Cheers,

Ian

Hmm, I think maybe we're at the point of needing to create a ticket?

Do you agree Drew?

If so, which tracker, git.sr.ht, todo.sr.ht, or somewhere else?

Thanks,

Ian

I tried this feature for the first time today, and it did not work for me either.

Both the git repo and tracker are in my account.

My commit[1] message was as follows, finishing with an "Implements: ..." line:

~~~
Complete Add Snippet screen.

This includes validating a new abbreviation before allowing it to be added.

Implements: https://todo.sr.ht/~ianmjones/snippetpixie/14
~~~

Awesome, thanks Adnan!

Ian

Hi Adnan,

I was just wondering, do you think kiln 0.3.0 is ready for release?

Selfishly, I'd love to see kiln 0.3.0 tagged so that it would eventually 
update the nixpkgs version, currently at 0.2.1. At the moment I have to 
use an overlay on NixOS to use 0.3.0, which is a little clunky in 
comparison to using a released version.

If there's anything blocking 0.3.0 being released, is there anything I 
can do to help?

Cheers,

Hey Adnan,

I've been using kiln via the master branch for a long time now. So over
the last few months I've used everything proposed for 0.3.0, right up
to having just published with 0.3.0-alpha-1-g3e1683e.

I've been building/installing it locally, and via builds.sr.ht when
publishing.

Everything has been working great, once I completed the updates to my
templates needed for the changes of course. 😉

So it's a big thumbs up from me for 0.3.0! 👍