On Fri, Apr 22, 2011 at 2:40 AM, Olivier Refalo <[email protected]>wrote:
> Can one of the developers explain the different elements involved in a > merge request. > From readin other threads, the poller is involved but I was wondering if > there was anything else. > This is how it works on a high level: - A merge request is added as a special branch (refs/merge-requests/id) in the *target* repository - A separate "tracking" repository is created for each *target* repository, containing one branch for each version of a merge request (refs/merge-requests/<id>/<version>) - When you push to a merge request (which is what the web UI does for you), the merge request branch in the target repository is updated to point to the new ending commit - When the merge request branch is updated, a new version is pushed to the tracking repository (triggered from the poller) - The poller also triggers the creation of events for the merge request > My issue, the request form doesn't show the list of commits. already > checked permissions, my poller runs as user GIT just like my repo. > Listing the commits should not require the poller to be running, it will load the commits directly from git. > Also, how does one activates detail logging ? > In config/environments/production.rb you should be able to change the line: config.log_level = :warn to config.log_level = :debug # or another log level, eg. :info Cheers, - Marius -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
