Currently, the function revision_log_by is implemented in storage but is exposed neither in the client nor the server. Wondering if it's intentional, and if not, if we could expose it correctly. It's useful to avoid making an extra request to the database in the web ui when looking for a revision with origin, probably among other things.
Description
Description
Revisions and Commits
Revisions and Commits
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T432 Expose revision_log_by in client and server | ||
| Migrated | gitlab-migration | T457 Add tests for revision_log_by |
Event Timeline
Comment Actions
Well, this implementation seems to be some dead code since it's:
- neither tested
- nor correct (it's calling inexistant code db.revision_log_by does not exist)
Anyway, i will investigate this tomorrow.