title: Integrating Gitlab with ReviewBoard - File Blob vs. Commit SHA1
body: <p>I'm trying to integrate Gitlab server that our company has been using with a new ReviewBoard server. From everything I've read about ReviewBoard setup, the most straightforward way to integrate git-like repositories is to use "Raw file URL mask" field if the repository has a web front end.</p>
  
  <p>Luckily, Gitlab, appears to support such a front end and even has a well documented public API:
  https:///api/v2/projects//repository/commits//blob?private_token=&amp;filepath=</p>
  
  <p>In ReviewBoard's repository setup, one can specify a custom URL that could be used to retrieve individual files from the git server.  This URL has two placeholders:</p>
  
  <ul>
  <li>{filename} - file path</li>
  <li>{revision} - sha1 of the file blob</li>
  </ul>
  
  <p>Unfortunately, I have learned that Gitlab's API expects SHA1 of the commit, not of the individual file and ReviewBoard as far as I can tell only sends SHA1 of the individual file but not of the commit</p>
  
  <ol>
  <li>Has anyone successfully integrated Gitlab with ReviewBoard?  If so, I'd be interested in hearing about it</li>
  <li>Is anyone aware of another, possibly undocumented, API call that Gitlab supports that would allow us to retrieve files based on SHA1 of the file blob?                                   </li>
  <li>Is anyone aware of a setting in ReviewBoard to force it to pass in SHA1 of the commit instead of the file blob?</li>
  </ol>