diff options
author | Arun Isaac | 2022-07-09 16:38:46 +0530 |
---|---|---|
committer | Arun Isaac | 2022-07-09 16:45:20 +0530 |
commit | fc8cf0ed8a5bd1507865df888a37ac5e90a46416 (patch) | |
tree | a3ca3075819531898d5d0d10afa5c408315fc4e1 /issues | |
parent | 693d4c492c760794df7186058f95e12f91cfc2be (diff) | |
download | tissue-fc8cf0ed8a5bd1507865df888a37ac5e90a46416.tar.gz tissue-fc8cf0ed8a5bd1507865df888a37ac5e90a46416.tar.lz tissue-fc8cf0ed8a5bd1507865df888a37ac5e90a46416.zip |
commit: Index commit messages too.
* tissue/commit.scm: New file.
* tissue/web/server.scm (%css)[.search-result-commit]: Add COMMIT
marker.
* bin/tissue: Import (tissue commit).
* tissue.scm (#:indexed-documents): Add commits.
* issues/index-commit-messages.gmi: Close issue.
Diffstat (limited to 'issues')
-rw-r--r-- | issues/index-commit-messages.gmi | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/issues/index-commit-messages.gmi b/issues/index-commit-messages.gmi index 54ab253..5c5ad12 100644 --- a/issues/index-commit-messages.gmi +++ b/issues/index-commit-messages.gmi @@ -5,3 +5,9 @@ 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? + +## Resolution + +Commit messages are now indexed. We can revisit indexing commit diffs and source code later, if need be. + +* closed |