How do you keep part of the project in a separate repository?



  • A private repository project is in place. The project is on the modules, and every module has a file of localization.

    The challenge is to separate the files for the interpreter. I mean, if you change the localization files, you could just intimidate the repositories with translations, and after the translator moves the files, get them back.

    And so that repositories don't get the code files.

    How can that be realized?



  • If, as a way of integrating repositories, consider the system https://git-scm.com/book/ru/v1/%D0%98%D0%BD%D1%81%D1%82%D1%80%D1%83%D0%BC%D0%B5%D0%BD%D1%82%D1%8B-Git-%D0%9F%D0%BE%D0%B4%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D0%B8 at least three options for the organization of the structure are possible:

    1. Create one repository where translation files for your modules will be sub-categories of species module1module2 et cetera and insert it as a git-podule, e.g. catalogue translations in, for example, the root of the main repository.
    2. Set up a few repositories on the number of your modules and connect them as git-ups in the sub-catalogs with your modules.
    3. Create one repository (with structure as the first option) and connect it in the form of git-podule in each catalogue with your modules.

    In any of these options, we're either gonna have to adjust the prefabricated crickets to indicate the changed ways to the files or to use symbolic references, but with symbolic references, as far as I know, are emerging. https://stackoverflow.com/q/5917249/4827341 ♪


    micro-instruction on git-submudule addition

    to add git repositories (available at url-репозитория() As a submodule in the current repository (which should not be subject to over-compromising changes), make a team:

    $ git submodule add url-репозитория каталог/куда/добавлять
    

    каталог/куда/добавлять must not exist at the time of the team, it will be automatically created.

    Once this team has been completed, the index will be automatically added каталог/куда/добавлять and a new (or modified, if you've already had any submodule) file. .gitmodules:

    $ git status
    

    On branch master

    Changes to be committed:

    (use "git reset HEAD <file>..." to unstage)

    new file: .gitmodules

    new file: каталог/куда/добавлять

    This change has to be filled.

    If necessary, you may send changes to the “core” repository team push..if the &quot; basic &quot; repository is used not only by you, but by the performance in the clones of this team repository pull You've got two more crews to do with your submodel. submodule init and submodule update:

    $ git submodule init
    Submodule 'каталог/куда/добавлять' (url-репозитория) registered for path 'путь/куда/добавлять'
    $ git submodule update
    Cloning into 'путь/куда/добавлять'...
    done.
    Submodule path 'путь/куда/добавлять': checked out 'хэш коммита'


Log in to reply
 


Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2