Skip to content
Snippets Groups Projects
Commit 71abb991 authored by Georges Racinet's avatar Georges Racinet
Browse files

Commit: lookup methods have to work with obsolete

The Rails app will store some changeset IDs and get back to HGitaly
for information after a while. For instance, this is what happens
with Merge Requests. It's perfectly possible that the changeset has
become obsolete in the mean time.

Hence the right thing to do is to make these commit methods work
on the unfiltered repository.

In order to mutualize, we're actually making the
`gitlab_revision_changeset` return also obsolete changesets if
queried by exact hash. This is consistent with the Git case: a
ref should never be obsolete, but an exact lookup can return
unreferenced commits.

In the tests, it was about time for the `make_empty_repo` helper
to activate the evolve extension. Thankfully no other test is
affected (without evolve, `amend` would strip the previous changeset)
parent 74f9767b
No related branches found
No related tags found
1 merge request!14Adjustments to pass Heptapod functional tests
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment