Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: One module one repo
by
dar
I LOVE the idea!
I have used git subrepo, too. It got a bit complicated after a while. I figure with one repo one module, there is not even a need for it.
To separate it, I already made that demo, with full history preserved: https://github.com/xoes-oca
Done with git subrepo ;-)
After that transition, using git submodules is just very fine. Stock git.
El mar., 18 jun. 2019, 8:32 p.m., Jose R. Prieto <joser.prieto@gmail.com> escribió:
I suggest use git subrepoI worked with it from a about two years, without problems.And we can have the current "project repositories" as a "meta repository" for specific subject, and inside it, one module with one individual repo (and isolated); and we will can choice between use the meta repository, or the individual; both for dev and deploy.I can make a very simple "demo", if you like the idea..Regards.PD:Simple notes about git subrepo and use:Git subrepo use.Install (recomended method):~$ git clone https://github.com/ingydotnet/git-subrepo /path/to/git-subrepo~$ echo 'source /path/to/git-subrepo/.rc' >> ~/.bashrcAdd a repository as a subrepo in a subdir of your repository:~$ git subrepo clone <repository> [<subdir>] [-b <upstream-branch>] [-f]Turn an existing subdirectory into a subrepo:~$ git subrepo init <subdir> [-r <remote>] [-b <branch>]Update the subrepo subdir with the latest upstream changes:~$ git subrepo pull <subdir>|--all [-b <branch>] [-r <remote>] [-u]Push a properly merged subrepo branch back upstream:~$ git subrepo push <subdir>|--all [<branch>] [-r <remote>] [-b <branch>] [-u]Fetch the remote/upstream content for a subrepo.:~$ git subrepo fetch <subdir>|--allCreate a branch with local subrepo commits:~$ git subrepo branch <subdir>|--allAdd subrepo branch to current history as a single commit:~$ git subrepo commit <subdir> [<subrepo-ref>]This "plumbing" command finds a common ancestor between two branches. It will look at the referenced tree hash in the commits to see if it can locate a common one:~$ git subrepo merge-base <branch1> <branch2>Get the status of a subrepo. Uses the --all option by default. If the -- quiet flag is used, just print the subrepo names, one per line:~$ git subrepo status [<subdir>]Remove artifacts created by fetch and branch commands:~$ git subrepo clean <subdir>|--ALL|--allEl mié., 19 jun. 2019 3:02, David Arnold <dar@xoe.solutions> escribió:Hi All,It looks like it's popping up again and again.So,ultimately, we may only delay it, I guess.Can I ask experienced OCA shoulders to advise on how to lay out a plan to get this done?In one year, 5 years, 10 years. Doesn't matter.Matters: get it eventually done.Best Regards,David_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
