BigW Consortium Gitlab

  1. 06 Feb, 2018 1 commit
  2. 29 Sep, 2017 2 commits
  3. 21 Sep, 2017 1 commit
  4. 23 Aug, 2017 2 commits
  5. 12 Jul, 2017 1 commit
  6. 29 Jun, 2017 1 commit
  7. 15 Sep, 2016 1 commit
  8. 05 Jul, 2016 4 commits
    • Rename ENV['PROTOCOL'] to ENV['GL_PROTOCOL'] to conform to what GitLab Shell… · 8b14d1d2
      Patricio Cano authored
      Rename ENV['PROTOCOL'] to ENV['GL_PROTOCOL'] to conform to what GitLab Shell expects and make the `protocol` param in `GitAccess` mandatory.
    • Improve the error message displayed when branch creation fails. · eb16e1e3
      Timothy Andrew authored
      Note: This feature was developed independently on master while this was
      in review. I've removed the conflicting bits and left the relevant
      additions, mainly a test for `Gitlab::Git::Hook`. The original commit
      message follows:
      
      1. `gitlab-shell` outputs errors to `stderr`, but we weren't using this
         information, prior to this commit. Now we capture the `stderr`, and
         display it in the flash message when branch creation fails.
      
      2. This can be used to display better errors for other git operation
         failures with small tweaks.
      
      3. The return value of `Gitlab::Git::Hook#trigger` is changed from a
         simple `true`/`false` to a tuple of `[status, errors]`. All usages
         and tests have been updated to reflect this change.
      
      4. This is only relevant to branch creation _from the Web UI_, since SSH
         and HTTP pushes access `gitlab-shell` either directly or through
         `gitlab-workhorse`.
      
      5. A few minor changes need to be made on the `gitlab-shell` end. Right
         now, the `stderr` message it outputs is prefixed by "GitLab: ", which
         shows up in our flash message. This is better removed.
  9. 04 Jul, 2016 2 commits
  10. 30 Nov, 2015 1 commit
  11. 14 Aug, 2015 1 commit