Fisheye style activity stream in Stash?

Neal Culiner
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 19, 2015

Hello,

We moved from SVN to Git and as Stash effectively replaces Fisheye we are trying to let go of Fisheye.  One thing we really like in Fisheye is you can view the commit activity in a nice feed style running list which also shows files affected.  In the Stash commits area you only see the commit and first line of the commit.  It's hard to see what files were touched in that commit so a "code owner" per se won't be alerted to someone touching an area of interest.

Is there an add-on or any way to get Fisheye style activity streams in Stash or even SourceTree?  We're learning Git but find it a little harder to get the big picture on files affected across multiple commits.

Thank you.

1 answer

0 votes
Daniel Wester
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 19, 2015

There are a couple of add ons on the marketplace:

https://marketplace.atlassian.com/plugins/ch.mibex.stash.rss4stash
https://marketplace.atlassian.com/plugins/com.stiltsoft.stash.graphs

That said - activity streams in Git are not equal to that as in SVN. In SVN when you send changes to to the central repository you're sending the explicit commits that happened. In Git, you're sending up a batch of commits. This means that if somebody only does a git push once a week - the activity stream might not show things properly. Depending on the implementation you might not see some changes (because the commit happened 24 hours ago) or you might see old changes as new (because the git push just happened on changes that happened last week). Just something to bear with. The commit graphs are much better for seeing the changes that affect multiple commits (at least IMHO).

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events