You can access a list of all commits within your repository for a specific branch and/or path.
|All commits on for specific ref||GET||/project/repository/commits/ref|
|All commits on a specific ref for a named path||GET||/project/repository/commits/ref/path/to/file/or/folder|
ref in this context can be a branch name, tag name or commit reference. If specified it will show the commits from that point in your history.
An array of commits will be returned when requesting the URLs listed above. Each commit will look similar to the data below:
<commit> <ref>40320d0d4f85fa7294a71e2d5291b8660f60c01f</ref> <message>add dev & staging to reserved domains</message> <author-name>Adam Cooke</author-name> <author-email>email@example.com</author-email> <authored-at type="datetime">2009-10-12T17:49:25+01:00</authored-at> <committer-name>Adam Cooke</committer-name> <committer-email>firstname.lastname@example.org</committer-email> <committed-at type="datetime">2009-10-12T17:49:46+01:00</committed-at> <parent-refs>48fe6489f9b68777aa36f1a6009b3039d4a7c234</parent-refs> <tree-ref>78ce1e531939b1c4e10820f8e1c293339208d3ee</tree-ref> <author-user>adam</author-user> <committer-user>adam</committer-user> </commit>
refis the commit reference or revision number
messagethe full message for this commit
parent-refsthe refs of all parent commits (git & mercurial only)
tree-refthe ref for the commit's tree (git only)
author|committer-useris the username of the appropriate Codebase user if one was matched with the email address
All other fields are self explanatory.