~hanna

Atlanta, United States

Transfem hobbyist developer. LGBT+ activist, software engineer, linux system administrator, and chocolate milk addict. She/her or fae/faer.

Recent activity

https://man.sr.ht/ does not display my current wikis 6 days ago

From Hanna to ~sircmpwn/sr.ht-discuss

I didn't even know this was a thing

[builds.sr.ht] Recursively initialize submodules when cloning 17 days ago

From Hanna to ~sircmpwn/sr.ht-discuss

Hello drew! Thanks for the quick reply, I have prepared a patch
following the directions you gave, it can be seen on the proper
email list[1]. Let me know if it looks good, thanks!

[1]: https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/32819

[PATCH builds.sr.ht] recursively initialize submodules 17 days ago

From Hanna to ~sircmpwn/sr.ht-dev

Updates the clone task to recursively init submodules rather
than only initializing at a depth of 1.

diff --git a/worker/tasks.go b/worker/tasks.go
index 022d60a..a1a2531 100644
--- a/worker/tasks.go
+++ b/worker/tasks.go
@@ -423,7 +423,7 @@ func (ctx *JobContext) CloneGitRepo(srcurl, repo_name, ref string) error {
	git = ctx.SSH("GIT_SSH_COMMAND='ssh -o " +
		"UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no'",
		"sh", "-euxc",
		fmt.Sprintf("'cd %s && git submodule update --init'", repo_name))
		fmt.Sprintf("'cd %s && git submodule update --init --recursive'", repo_name))
	git.Stdout = ctx.LogFile
[message trimmed]

[builds.sr.ht] Recursively initialize submodules when cloning 18 days ago

From Hanna to ~sircmpwn/sr.ht-discuss

Currently the CI seems to only clone at a depth of 1, meaning that if any
submodules have submodules themselves, they aren't pulled into the
repository as well. This can be slightly problematic for certain projects
and while certainly it's possible to do it yourself as I am in my current
project[1], it would be a lot more convienient if the setup step did this
itself, perhaps behind a manifest flag or just enabled by default.

[1]: https://git.sr.ht/~hanna/toxin/tree/devel/item/.build.yml#L10

todo.sr.ht generates emails to an unsuspecting SourceHut user 21 days ago

From Hanna to ~sircmpwn/sr.ht-discuss

Usually Drew asks people to submit patches to the sr.ht-dev list[0], as all patches
are usually submitted and reviewed there. I would recommend submitting the
patch there instead of here, as this list is mainly just for discussion not for anything
development related, would also have a higher chance of been seen in the list.

[0]: https://lists.sr.ht/~sircmpwn/sr.ht-dev

[PATCH] I'm about to try git send-email 24 days ago

From Hanna to ~sircmpwn/email-test-drive

---
 hanna | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 hanna

diff --git a/hanna b/hanna
new file mode 100644
index 0000000..66cb3d4
--- /dev/null
+++ b/hanna
@@ -0,0 +1 @@
I have successfully used git send-email!
-- 
2.36.0
[message trimmed]

[PATCH v2] fixing stuff 24 days ago

From Hanna to ~sircmpwn/email-test-drive

---
 hanna | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hanna b/hanna
index 6d0ecfd..66cb3d4 100644
--- a/hanna
+++ b/hanna
@@ -1 +1 @@
I'm about to try git send-email
I have successfully used git send-email!
-- 
2.36.0
[message trimmed]

[PATCH] testing git send-email 24 days ago

From Hanna to ~sircmpwn/email-test-drive

From: Hanna <xhxnna@proton.me>

---
 hanna | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 hanna

diff --git a/hanna b/hanna
new file mode 100644
index 0000000..6d0ecfd
--- /dev/null
+++ b/hanna
@@ -0,0 +1 @@
I'm about to try git send-email
[message trimmed]

Showing git commit sign status on logs 25 days ago

From Hanna to ~sircmpwn/sr.ht-discuss

> There is a ticket open for this: https://todo.sr.ht/~sircmpwn/git.sr.ht/170

Oh thanks, I didn't see it. If I knew the architecture well enough I'd help implement it.

Showing git commit sign status on logs 25 days ago

From Hanna to ~sircmpwn/sr.ht-discuss

Not sure if this is something that would be desirable, probably not given it 
hasn't been added. However, I was wondering if there's any reason for not
showing whether or not commits are signed on git.sr.ht, similar to other forges
such as Gitea, Gogs, GitHub, etc. To be specific I'm talking about showing
something that shows commits are "verified" such as on GitHub[0]. Where it
shows that a commit is signed by a PGP/GPG key that has an email that matches
the commit author. It's a very niche feature, but I've always liked it.

[0]: https://transpri.de/i/d5me6woo.png