From 8ae970c92ed71789ac746b3ae43251cfdd3498bb Mon Sep 17 00:00:00 2001
From: Sebastian Kuzminsky <seb@highlab.com>
Date: Mon, 7 Jul 2025 22:47:18 -0600
Subject: [PATCH] update 'description' in issue
 acb06210852087afceaf4d9e015e3c6b

---
 .../comments/acb06210852087afceaf4d9e015e3c6b/description    | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 75cefad80aacbf23fc7b9c24a75aa236/comments/acb06210852087afceaf4d9e015e3c6b/description

diff --git a/75cefad80aacbf23fc7b9c24a75aa236/comments/acb06210852087afceaf4d9e015e3c6b/description b/75cefad80aacbf23fc7b9c24a75aa236/comments/acb06210852087afceaf4d9e015e3c6b/description
new file mode 100644
index 0000000..8c82c0f
--- /dev/null
+++ b/75cefad80aacbf23fc7b9c24a75aa236/comments/acb06210852087afceaf4d9e015e3c6b/description
@@ -0,0 +1,5 @@
+> should we also add timestamps to the comments in text? or should we just rely on the filesystem/git time?
+
+I think the "creation time" of a comment is the commit time of the oldest
+commit that touches the comment.  We can get this from something like:
+$ git log --pretty=format:%at entomologist-data -- ${ISSUE}/comments/${COMMENT}