summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArun Isaac2022-07-08 02:00:13 +0530
committerArun Isaac2022-07-08 02:00:13 +0530
commitf6dc5952e5f5c644cd7c4f15c9705859c3fb2c8a (patch)
treea6ecea519b63665b49e05dcaa3cd83a2700fe4c1
parentf281238321377710b99a78671287d2ae6a58338c (diff)
downloadtissue-f6dc5952e5f5c644cd7c4f15c9705859c3fb2c8a.tar.gz
tissue-f6dc5952e5f5c644cd7c4f15c9705859c3fb2c8a.tar.lz
tissue-f6dc5952e5f5c644cd7c4f15c9705859c3fb2c8a.zip
issues: Request indexing commit messages.
* issues/index-commit-messages.gmi: New file.
-rw-r--r--issues/index-commit-messages.gmi7
1 files changed, 7 insertions, 0 deletions
diff --git a/issues/index-commit-messages.gmi b/issues/index-commit-messages.gmi
new file mode 100644
index 0000000..54ab253
--- /dev/null
+++ b/issues/index-commit-messages.gmi
@@ -0,0 +1,7 @@
+# Index commit messages
+
+* tags: enhancement
+
+Currently, we only index issues and other documents. We could also index commit messages. If a project is in the habit of writing long detailed story-like commit messages, this feature could be very useful. I have always been frustrated by the lack of stemming when searching commit messages with git log --grep.
+
+If we can index commit messages, could we even index commit diffs and source files as well? Perhaps there is something about source code that makes it harder to index?