An error occurred fetching the project authors.
  1. 29 Nov, 2013 1 commit
  2. 28 Nov, 2013 1 commit
  3. 27 Nov, 2013 1 commit
  4. 16 Oct, 2013 1 commit
  5. 14 Oct, 2013 1 commit
  6. 18 Sep, 2013 1 commit
  7. 26 Aug, 2013 1 commit
  8. 21 Aug, 2013 2 commits
  9. 17 Jul, 2013 1 commit
  10. 19 Jun, 2013 1 commit
  11. 13 Jun, 2013 3 commits
  12. 11 Jun, 2013 1 commit
  13. 31 May, 2013 1 commit
  14. 28 May, 2013 1 commit
  15. 24 May, 2013 1 commit
  16. 14 May, 2013 1 commit
  17. 02 May, 2013 1 commit
    • Stephen Lottermoser's avatar
      Internally public projects · 4c44c5ef
      Stephen Lottermoser authored
      Public projects listed in the public section will be linked to the
      actual project's page. Public projects now give any user Guest
      permissions to the project, allowing them to download the code, read
      and create issues, and view anything else in the project's pages.
      
      Ample access tests have been added to the project_access_spec to
      verify correct permissions and behavior on public projects.
      - Visitors to the site who are not logged in still cannot view the
        project's pages.
      - Logged-in users visiting a public project where they are not a team
        member can create issues, but not snippets. They can view the projects
        code, issues, merge requests, etc, just as if they were a Guest member
        of the project.
      - Since this is a public project, the user is also granted :download_code
        permissions, a permission normally reserved for Reporters, since they
        can clone the repo anyways and browse commits and branches locally.
      4c44c5ef
  18. 24 Apr, 2013 1 commit
  19. 14 Mar, 2013 1 commit
  20. 13 Mar, 2013 2 commits
  21. 04 Mar, 2013 1 commit
  22. 28 Feb, 2013 1 commit
  23. 04 Feb, 2013 1 commit
  24. 02 Feb, 2013 1 commit
  25. 25 Jan, 2013 1 commit
  26. 24 Jan, 2013 1 commit
  27. 03 Jan, 2013 1 commit
  28. 05 Dec, 2012 1 commit
  29. 29 Nov, 2012 1 commit
  30. 24 Nov, 2012 2 commits
  31. 23 Nov, 2012 1 commit
  32. 22 Nov, 2012 1 commit
  33. 06 Nov, 2012 1 commit
  34. 10 Oct, 2012 1 commit
    • Robb Kidd's avatar
      Separate observing of Note and MergeRequests · 16ceae89
      Robb Kidd authored
      * Move is_assigned? and is_being_xx? methods to IssueCommonality
      
        This is behavior merge requests have in common with issues. Moved
        methods to IssueCommonality role. Put specs directly into
        merge_request_spec because setup differs for issues and MRs
        specifically in the "closed" factory to use.
      
      * Add MergeRequestObserver. Parallels IssueObserver in almost every way.
      
        Ripe for refactoring.
      
      * Rename MailerObserver to NoteObserver
      
        With merge request observing moved out of MailerObserver, all that
        was left was Note logic. Renamed to NoteObserver, added tests and
        updated application config for new observer names. Refactored
        NoteObserver to use the note's author and not rely on current_user.
      
      * Set current_user for MergeRequestObserver
      
        IssueObserver and MergeRequestObserver are the only observers that
        need a reference to the current_user that they cannot look up on
        the objects they are observing.
      16ceae89
  35. 26 Sep, 2012 1 commit