Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-2902

Add pull / merge requests to fisheye

    XMLWordPrintable

Details

    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      With the recent acquisition of BitBucket, you may already be doing this – this request is to add "pull request" tracking to FishEye.

      This would enable better implementation of the "integrator workflow" (see http://progit.org/book/ch5-1.html)

      Merge/Pull requests could show up as a task in your dashboard (with accompanying e-mail notification), alerting you that someone wants to you to merge (pull) changesets from one repo/branch to another. You then have a nice web-based conversation, tell the person to fix their whitespace damage (or critical bug they missed, etc) and perform a mini-code-review prior to a merge. You could do this with Crucible today, but a) not everyone has crucible, b) the UI is too involved, too many clicks.

      "hg outgoing" shows you the changes in your repo/branch that are not in the other repo – this just needs some nice UI to make it easier from the web interface.

      Examples of pull/merge requests include the following

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              2305d89f2c0c Sam Post
              Votes:
              19 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated: