Add Support Gems / Subprojects

[williscool]

Some times the bugs happen in gems you worked on.

It would be cool to be able to have the git blame run on the the repo of that gem and analyize it

[RISCfuture]

What kind of analysis are we talking about? If you just want to display code context on the website, that's one thing, but if it's used for fault analysis, that's kind of a confusing problem, because most gems are authored by people external to the company, and therefore who probably don't want to be emailed every time someone who is just using their gem has a bug :)

[williscool]

True about the email thing lol.

I just meant would be nice to be able to have squash run git blame on certain gems if you set it up to.

You probably wouldn't have those email by default and maybe have a whitelist for who it would email (maybe on emails from a certain domain. i.e. *@yourcompany.com)

The original idea came from working on an application that uses

https://github.com/ging/social_stream

The issue is this particular framework generates a rails application that you use but a lot of the code (and so invariably the bugs) are in the gem of the framework itself.

As opposed to the application it generated.

So it would be nice to be able to pinpoint origins in those.