-
Suggestion
-
Resolution: Done
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.
- 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...
[BSERV-2810] Option to squash commits when merging a pull request
Workflow | Original: JAC Suggestion Workflow [ 3395629 ] | New: JAC Suggestion Workflow 3 [ 3617569 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: BSERV Suggestions Workflow [ 2685605 ] | New: JAC Suggestion Workflow [ 3395629 ] |
Workflow | Original: Stash Workflow [ 445869 ] | New: BSERV Suggestions Workflow [ 2685605 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 291486 ] |
Attachment | New: squash-latest.png [ 219599 ] |
Remote Link | Original: This issue links to "Page (Extranet)" [ 190335 ] |
Assignee | New: Christian [ crolf ] |
Description |
Original:
{panel:title=Atlassian status as of May 2015|borderStyle=solid|borderColor=#3C78B5 | titleBGColor=#3C78B5 | bgColor=#E7F4FA }
Hi everyone, Thanks for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Stash. This suggestion is a priority for the Stash development team and is on our roadmap, however we're not able to provide a timeline for when it will be resolved. Product feedback is collected from a number of different sources and is evaluated when planning the product roadmap. You can [learn more about our process here|https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com]. Cheers, Roger Barnes Product Manager - Stash {panel} *Original request description:* The pull requests are a nice feature, but not only do we still need to delete branches manually (see issue 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. |
New:
The pull requests are a nice feature, but not only do we still need to delete branches manually (see issue 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. |
Fix Version/s | New: 4.9.0 [ 62412 ] | |
Resolution | New: Done [ 17 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 190335 ] |