Best practices to maintain plugin source codes on Github

Hi,

Currently we maintaining plugin source using svn and we are planning to move all out plugin sources to github.

Currently our repository structure is like below in svn.

Nop3.80
|
|--> Plugin1
|--> Plugin2
|--> Plugin3

Nop3.90
|
|--> Plugin1
|--> Plugin2
|--> Plugin3

Nop4.00
|
|--> Plugin1
|--> Plugin2
|--> Plugin3

There is only one repository and under that repository we maintain folder wise structure. So that we can only checkout particular folder and add it as project in relevant nopCommerce code
we don't maintain whole NopCommerce source code. we just maintain plugin source codes.

But in Github, we don't find any way to checkout only one folder from the whole repository.

We just want to know how you guys maintain plugin source code in github in case of multiple plugins and their difference version of nop involve?

We are using git branches to manage versions. I have a blog post explaining our workflow that might be helpful https://www.majako.net/managing-nopcommerce-plugins-with-git-submodule

mgustafsson wrote:

Thanks a lot for your nice suggestion.

We will be doing in a same way as you suggested.