Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Done
Fix Version/s: 4.9.0
Component/s: Pull Requests
Labels:
- pr-merge

Feedback Policy:

We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

The pull requests are a nice feature, but not only do we still need to delete branches manually (see issue ~~STASH-2753~~), it is also not possible to squash the new commit into the target branch.
We would like to have a clean history that doesn't show any parellel commits in our main development and master branches.

It seems that this is relatively easy to implement, since it is a new button and a few extra git commandline calls. But that is from a user point of view.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

squash-latest.png
86 kB
03/Jan/2017 8:17 PM

Issue Links

has a derivative of

BSERV-3093 Repository setting for merge strategy when merging a pull request

Closed

is duplicated by

BSERV-3350 Ability to squash commits from UI

Closed

is related to

BSERV-2753 Option to delete a branch after pull request merge

Closed

BSERV-2873 As a Stash user, I want to rebase prior to merging a Pull Request

Closed

relates to

BSERV-2857 Pull Request should not force --no-ff flag

Closed

BSERV-6913 Change "declined" to a friendlier verb or add a new pull request status.

Closed

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(1 relates to, 6 mentioned in)

Activity

People

Assignee:: Christian

Reporter:: Paul B. Omta

Votes:: 307 Vote for this issue

Watchers:: 171 Start watching this issue

Dates

Created:: 01/Nov/2012 9:45 AM

Updated:: 19/Sep/2019 5:49 AM

Resolved:: 30/Aug/2016 3:11 AM