Luis Here's another one: https://kagi.com/search?q=git+rebase_head
Search: git REBASE_HEAD
Context: In a Git directory, a file may exist called REBASE_HEAD which seems to point at a commit which I'm currently editing. I want to know whether a script can rely on the existence and contents of REBASE_HEAD to assess whether an interactive rebase edit is currently underway on the correct commit. I was looking for some documentation which would go into more detail (it's not covered by man git-rebase).
The results include https://docs.github.com/en/get-started/using-git/using-git-rebase-on-the-command-line which does contain the words rebase and head, but not in the same context as each other.
I guess I can understand if a search engine strips out punctuation like underscores, but it should preserve the fact that rebase and head were connected to each other by an underscore. That means, in results, those tokens should be separated by at most one non-alphanumeric character, not just happening to share a whole page with each other.
Maybe kagi can offer a "temperature" setting which increases the sensitivity and decreases the specificity of results? If other people want git rebase_head to be synonymous with git OR rebase OR head I don't want to stop them, but I do want to turn the temperature down and have stricter results by default for myself.
Edit: Just a note to add, the page which I think Kagi should have returned is https://git-scm.com/docs/gitrevisions. That's the official Git documentation explaining REBASE_HEAD, which is exactly what I wanted.
