You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
So we are evaluating Fisheye.
Our git repos are large, with 12 or more submodules, some using LFS.
When devs implement a feature, they may change one or more submodules, as well as the parent project which will use the updated APIs from the submodules; the changes are tightly coupled.
I'm trying to work out a usage paradigm for this - I appreciate that when a developer commits a change to the parent repo, changing the revision/commit of a sub module, they might be using the work of someone else, and mandating that a review includes the changes on the submodule commit is not valid.. but it would be nice to have that option.
Is the way we're supposed to use it basically unrolling our tree and adding all the submodules and parent repos separately, maybe gathering them together in a FishEye project? Then picking up the separate commits into a single review?
Hi @kevin conroy,
While I don't have the answer to all your questions, let me share with you that submodules are not fully supported in Fisheye.
There is an existing feature request here:
You can join the conversation there as well as see if the comments on the request help to clarify some of your points.