Skip to main content

Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #13279 Add no-ff strategy for merging pull-request (needed for gitflow)
    Infos
    #13279
    Guilhem Bonnefille (CS) (gbonnefille)
    2022-10-24 13:52
    2019-04-18 09:11
    14155
    Details
    Add no-ff strategy for merging pull-request (needed for gitflow)
    Currently the proposed strategies to close a pull request are:
    - default (fast-forward or merge if fast forward is not possible)
    - fast-forward only

    It would be great to let teams decide a no-fast-forward strategy in order to force a commit merge, even if fast forward is possible. This is the recommanded approach for Git workflow like GitFlow (https://nvie.com/posts/a-successful-git-branching-model/)

    Internet is full of articles about no-ff vs rebase, but letting teams decide their strategy is certainly the most important for Tuleap.
    Pull Request
    11.0
    EL7 (CentOS|RHEL)
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2022-10-24
    Attachments
    Empty
    References
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2022-10-24 13:52

    I close this request as it's now tracked as a user story

    • Status changed from New to Closed
    • Connected artifacts
    • Close date set to 2022-10-24