Vote #63912
未完了Display Git Submodule
0%
説明
Redmine should provide to users a way to navigate on git submodules. Actually it displays a submodule as a simple file. I think redmine should navigate on submodules as part of the project.
journals
Leandro Nunes dos Santos Nunes wrote:
> Redmine should provide to users a way to navigate on git submodules. Actually it displays a submodule as a simple file. I think redmine should navigate on submodules as part of the project.
An example so that I could understand the problem ? I don't really use git.
--------------------------------------------------------------------------------
Nicolas Chuche wrote:
> An example so that I could understand the problem ? I don't really use git.
A git submodule is basically a pointer to another git repository. If you are familar with svn, they are simialr to svn externals.
Example:
* my_git_repo/
* my_git_repo/stuff/
* my_git_repo/third_party_library/ => submodule to http://foo.bar/library.git
* my_git_repo/third_party_library_2/ => submodule to http://foo.bar/library_two.git
This proposal is asking for Redmine to pull in the submodules so their contents can be browsed in Redmine.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
another +1 .. I'd love to see this.
--------------------------------------------------------------------------------
I would _not_ want the content from submodules to be pulled into the super project. If one is interested on the code of (one or more) submodules, they should be tracked as their own (separate) redmine projects.
A special icon to point out that a certain file is a submodule pointer is perfect imho. A click could go to the repo (if it's here). Github does the same (e.g. dataset in "radiant vendor plugins":http://github.com/radiant/radiant/tree/4b817a8b533f095bdd6354ccec7acc4e6b1677c0/vendor/plugins).
--------------------------------------------------------------------------------
Hans-Peter Suter wrote:
> I would _not_ want the content from submodules to be pulled into the super project. If one is interested on the code of (one or more) submodules, they should be tracked as their own (separate) redmine projects.
I totally agree with Hans-Peter. We are tracking submodules with redmine subprojets, which works perfectly.
--------------------------------------------------------------------------------
I'm starting to work on this: http://github.com/asoltys/redmine/commits/git_submodules
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1 for "A special icon to point out that a certain file is a submodule pointer is perfect imho. A click could go to the repo (if it's here)."
--------------------------------------------------------------------------------
Any updates on this?
+1 from me too
--------------------------------------------------------------------------------
Hi,
I have written a patch for displaying submodules and linking them to the repository.
Configuration:
add main repository,
add submodules with identifier being the submodule name as integrated into main repository
https://github.com/bastie87/redmine
--------------------------------------------------------------------------------