On the https://man.sr.ht/wiki/create/ref page, in the "Or choose an existing ref" sexion the links end in /refs/heads/branch, which 404s: https://git.sr.ht/~nabijaczleweli/klapki/refs/heads/trunk.

/log/branch or /tree/branch might be better.

https://git.sr.ht/~sircmpwn/man.sr.ht/tree/30ec60bd1489c90f70e1c5eddf0399586b43b6a9/mansrht/templates/new-wiki.html#L15

sure

Dupe of #34

Well, now you can't, but as you can see in the patch, that page had always linked to git.sr.ht.

Hilariously, the links on that page lead me to https://git.sr.ht/~nabijaczleweli/$REPONAME

https://git.sr.ht/~urandom/errors says:

<meta name="go-import" content="git.sr.ht/~urandom/errors git https://git.sr.ht/~urandom/errors">

but https://hg.sr.ht/~urandom/cd8eb6bf-7e0f-4208-8b82-2680640ebd62 says:

<meta name="go-import" content="hg.sr.ht/~urandom/cd8eb6bf-7e0f-4208-8b82-2680640ebd62 hg https://hg.sr.ht/~urandom/cd8eb6bf-7e0f-4208-8b82-2680640ebd62.hg">

the solution is likely to be just applying this diff:

diff -r 362b357bfe8b hgsrht/templates/repo.html
--- a/hgsrht/templates/repo.html        Thu Aug 20 10:17:06 2020 -0400
+++ b/hgsrht/templates/repo.html        Fri Sep 04 23:59:38 2020 +0200
@@ -13,7 +13,7 @@
 {% block head %}
 {{ super() }}
 {% if clone_urls %}
-<meta name="go-import" content="{{domain}}/{{owner.canonical_name}}/{{repo.name}} hg {{clone_urls[0]['url']}}.hg">
+<meta name="go-import" content="{{domain}}/{{owner.canonical_name}}/{{repo.name}} hg {{clone_urls[0]['url']}}">
 {% endif %}
 {% endblock %}

Fun fact about the new CSP: it blocks Stripe's JS at https://meta.sr.ht/billing/new-payment, so the page is mostly empty.

Pushing a bad manifest now does something comparable to pushing one to a git repo:

nabijaczleweli@tarta:~/uwu/quickly$ hg push nab
pushing to ssh://hg@hg.sr.ht/~nabijaczleweli/quickly
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 0 changes to 0 files
remote: Failed to submit build job  alpine.yml:
remote:         mapping values are not allowed here
remote:   in "<byte string>", line 4, column 13:
remote:      epositories:
remote:                 ^

~umgeher: in your case, that message says "DKIM signature: fail" in the UI, which is confirmed by this header added by Postfix at sourcehut:

Authentication-Results: mail-b.sr.ht;
	dkim=fail reason="key not found in DNS" (0-bit key) header.d=umgeher.org header.i=@umgeher.org header.b=gszn4mXZ

which may very well be because your DKIM key is CNAMEd, but that's beside the point: ``` nabijaczleweli@nabtop:~$ dig -t txt key1._domainkey.umgeher.org key1._domainkey.umgeher.org. 3600 IN CNAME key1.umgeher.org._domainkey.migadu.com. key1.umgeher.org._domainkey.migadu.com. 2999 IN TXT "v=DKIM1; k=rsa; " "p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtHUGqFcWxRsjz1gU2YezZugtoElhKiSnEZv2JrMI91vCx7MCikVYNC6fTofr38mLecCKMJ6Wh++ZYhfAfBlH+qILmUIe/r7Ek/bq7x1/Iz+smbAGF/1+v0ftcebzQYGSxPxakExvjdQi06fbEYq87NMA9CWuxEVSRJZHhCqdJdNifWTKXQGcmkX/yrR8nLIcy7YH3I6p7xoaXe9CW" "ggb9Fu4gA46VyPG3sA2fHU/kGA6aLP9R7LRJK2AsNUonjKdiS46y7fzc0JU/Iv8Iz5LtIOaEc8/QGiUz8wqd/t6Qk24SU50IHkXP7ONQ8W3LdoWy7n509oRbzcCupXBZ4aVkQIDAQAB"

OTOH ~josealberto4444's message has both a DKIM signature *and* a mark that it's correct (though, IIRC, the signatures are verified separately from the headers), but that isn't reflected in the UI.