allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zeromus" <>
Subject [allura:tickets] #7681 git fork workflow improvement suggestions
Date Thu, 11 Sep 2014 19:23:48 GMT


** [tickets:#7681] git fork workflow improvement suggestions**

**Status:** open
**Milestone:** limbo
**Created:** Thu Sep 11, 2014 07:23 PM UTC by zeromus
**Last Updated:** Thu Sep 11, 2014 07:23 PM UTC
**Owner:** nobody

This was motivated by a user who wanted to delete a git fork, and needed guidance to find
it in the user tools area. This is not an obvious thing at all and only makes sense if you
understand the internal allura organization. It seemed there was a simpler way (item #4) we
could direct him to it. The rest of these items I discovered while writing up #4
1. : From this page, it is not clear that to _edit_
a tool, I have to pick [Add Tools]. The button should be called [Edit Tools] and one would
assume that you can add tools from there. 
2. There should be a page you can generate for every installed tool which would just contain
a list of commands--the same list of commands printed for every tool at
. For example, . This will be useful
for item #4
3. For the git tool, there is no way to get
to the actual fork page. This is odd, because from
, I could _only_ get to the actual fork page. There should be a command on the git tool called:
Visit Fork Page
4. There is no way to way to delete a git fork from the fork's page. There is a little list
of commands (fork, request merge), but some users expect the full assortment of commands (which
are currently only visible from the tools administration page) to appear here. A simple way
to effect this would be to add a link to the fork page called [ Config ] or [ Admin ] which
would take you to the appropriate place in the tools administration. Now, the ideal destination
for this link is the described in
item #2. If it goes to instead, then the user
is forced to look through unrelated administration stuff before finding the options for the
git repository/fork that he was just looking at. However... it's not the end of the world.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message