Split repository

[jycr]

As discussed on Slack, repositories should be split based on languages and/or platform. This is so that each plugin can have its own development cycle.

For the "code" part, I found several methods:

• GitHub Docs - Splitting a subfolder out into a new repository
• How to split a git repository into two different ones
• Splitting Your Git Repo While Maintaining Commit History
• Git — How to Split Git SubDirectory into Separate Repository?
• Difference between git filter-branch subdirectory-filter & git subtree split -P

To migrate issues, I found this:

• GitHub Docs - Transferring an issue to another repository

[zippy1978]

Thanks @jycr ,

As iOS has not much history, maybe we can rename this one as android, and I can start moving iOS to another repo ? This way, we won't loose stars and issues / history.

What do you think ?

[dedece35]

hi @jycr @zippy1978 why not to create a new one for ios (ecoCode-ios) and rename the current ecoCode-mobile to ecoCode-android. but the problem will be in the versionning system : currently, ecoCode-mobile is 1.0.1. If we rename the repository, what will be the new version for ecoCode-android ? 1.1.0 ? 2.0.0 ? and for ecoCode-ios ? 1.1.0 ?

I've just created the repository ecoCode-ios with the minimum files got from current ecoCode-mobile repository. I configure the settings like ecoCode-mobile

[zippy1978]

Hi, I made to PRs to finalize the migration (iOS plugin removal on ecoCode-mobile, and release 1.1.0 on ecoCode-ios), here they are:

• https://github.com/green-code-initiative/ecoCode-mobile/pull/68
• https://github.com/green-code-initiative/ecoCode-ios/pull/4