I was just going through and I believe we might face the following problem 
while implementing this. 

We will need to check if there are multiple SCM tools since the ticket tool 
might be used for multiple ones. And this might be difficult to implement since 
Allura does not have a one-to-one relationship with the SCMTools and the 
Trackers.

For example: https://sourceforge.net/p/texstudio/ which has two trackers and 
two mercurial sources.

Maybe we could provide some way for branches to be able to be deleted from the 
web interface. For example github provides for it in repo/settings/branches
We could do the same under SCMtool/settings/branches in 
https://forge-allura.apache.org/p/allura/git/ref/master/branches/

This would reduce the number of stale branches that have already been merged 
into the codebase and solve the problem you were mentioning. 

Also, we can have a way to change the branch by searching like the one in 
github.
![Imgur](http://i.imgur.com/gwSooV4.png)

and also to create branch there if there is proper write access:
![Imgur](http://i.imgur.com/OK9uGqE.png)


---

** [tickets:#8116] Branches directly from Tickets.**

**Status:** open
**Milestone:** unreleased
**Created:** Thu Aug 11, 2016 07:49 PM UTC by Pranav Sharma
**Last Updated:** Fri Aug 12, 2016 08:43 PM UTC
**Owner:** Pranav Sharma


One of the basic and maintainable style followed by teams is to create branches 
related to tickets, and limiting the creation of branches. I think this is a 
common trend and we should make a feature which would add an option on tickets 
page to instantly create a new branch from desired base. I believe this would 
help definitely to manage rogue branches even for frequent committers. Also it 
helps to directly match what code changes are related to a particular ticket. 

This would be completely optional and a team can switch it on only if they 
would want to limit and manage branches.

Any suggestions are welcome.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed 
to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.

Reply via email to