Bugzilla – Full Text Bug Listing
| Summary: | [server] Provide REST API for git log | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Tomasz Zarna <tomasz.zarna> |
| Component: | Git | Assignee: | Szymon Brandys <Szymon.Brandys> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 334213, 339105, 340051, 340052, 340053 | ||
I released changes. The current shape of API is: 1) GET /git/commit/[refId]/file/[pathToFile]?parts=body will return the commit content 2) GET //git/commit/[refId]/file/[pathToFile] will return a log with commits from the first commit to the given refId The next thing to do is to 1) parameterize GET so we could specify the full range for the log (Bug 340052) 2) try to return a multi-part response containing both the commit content and details (author, message, etc.) (Bug 340053) 3) revisit tests and add/enable those for git log (Bug 340051) FYI : I used low level JGit API instead of LogCommand. LogCommand does not allow to filter commits using file paths. See Bug 340049. |
Could be implemented as GET /git/commit/file/{projectId}/[{path}].