~boehs

https://boehs.org

#Evan Boehs

he/him

One Push to rule them all, one Pull to find them, one Merge to bring them all and in the Repo bind them.

See https://sr.ht/~boehs/boehs for smaller projects

Trackers

~boehs/srht-patches

Last active 2 months ago

~boehs/site

Last active 2 months ago

~boehs/boehs

Last active 3 months ago

~boehs/oasis

Last active 3 months ago

~boehs/kipos

Last active 7 months ago

#3 to-do labels as multiple select instead of single select 2 months ago

Ticket created by ~boehs on ~boehs/srht-patches

#2 ENV variable for branch commit that triggered build (and maybe the commit hash) 2 months ago

Ticket created by ~boehs on ~boehs/srht-patches

19:40:28 <dhruvin> builds.sr.ht checks out a particular commit in a build job; in response to a push to git.sr.ht repository. How do I get what branch was that commit pushed to? (`git branch --show-current` does not work)
20:34:18 <alderwick> dhruvin: in my case I wanted to skip a build step if we're not building the main branch, so I have the line “if [ "$(cd uxn && git rev-parse HEAD)" != "$(cd uxn && git rev-parse origin/main)" ]; then exit; fi” in my .build.yml
20:38:27 <dhruvin> I used [ "$(cat .git/HEAD)" != "$(cat .git/refs/heads/master)" ] as a workaround, but yours will work with non-detached HEAD as well. I'll change mine to that. Thanks.

#1 Alt texts for build statuses 2 months ago

builds added by ~boehs on ~boehs/srht-patches

#1 Alt texts for build statuses 2 months ago

Ticket created by ~boehs on ~boehs/srht-patches

On builds we get an svg for an X or an O, depending if the task succeeds. Is it possible to have something like <img alt...> for those?

Via rkta on irc

#31 look into h-card 2 months ago

Comment by ~boehs on ~boehs/site

Evan Boehs referenced this ticket in commit d76b47a.

REPORTED RESOLVED IMPLEMENTED

#22 Randomly `___LIQUID0___` in codeblocks 2 months ago

Comment by ~boehs on ~boehs/site

34964c2 did not fix it

#22 Randomly `___LIQUID0___` in codeblocks 2 months ago

Comment by ~boehs on ~boehs/site

Evan Boehs referenced this ticket in commit 34964c2.

#22 Randomly `___LIQUID0___` in codeblocks 2 months ago

Comment by ~boehs on ~boehs/site

Someone opened an issue about this:

and they got a {% raw %} suggestion that worked for them... the lucky bastard.

#22 Randomly `___LIQUID0___` in codeblocks 2 months ago

Comment by ~boehs on ~boehs/site

Well, the obvious solution is {% raw %}, but we are doing this already:

But compare this to

and well

#22 Randomly `___LIQUID0___` in codeblocks 2 months ago

Comment by ~boehs on ~boehs/site

On pages with blog posts containing {{liquid tags}}, they get replaced with ___LIQUIDX___. This is because of obvious reasons. Well, at first.

I think it is probably a race condition, everything works fine if the syntax highlighter gets there first? I think? But then if liquid does it's thing and during that, code blocks happen then it breaks? No clue