Last modified: 2013-06-09 22:55:06 UTC
As far as I can determine, Gitblit currently only tracks merged changes. Gerrit's ability to query for a commit hash independent of its status has gotten people accustomed to using commit hashes to refer to changes. This becomes problematic if Gitblit is used (in templates, etc.) to construct permanent URLs to changes, as Gitblit does not currently track unmerged changes, meaning the change referenced in the URL is not resolved and the user is silently redirected to the main page.
Um, it should track everything, since Gerrit links to it on unmerged changes. The summary page and log may not show a running list of unmerged things but I'd be willing to guess those pages only watch refs/heads/ and refs/tags/ (I'll note the behavior in Gitweb was identical here)
(In reply to comment #1) > Um, it should track everything, since Gerrit links to it on unmerged changes. Yes, you're right. I mis-diagnosed the problem. It ended up being something unrelated (the URL to the commit included non-URL-encoded slashes, which threw off GitBlit).
