When processing folders, the /local folder will always have a priority over /bitrix. templates - templates of websites, templates of components, and templates of pages.php_interface - init.php, folder user_lang.activities - actions of the production project.Actually, it will suffice to add one folder /bitrix to the exemptions. It will permit to separate changing project files from the product folder. Support of the /local Folderįor the convenience of project developers, main project files are transferred from the folder /bitrix to the folder /local as a part of work on the new kernel D7 starting from kernel version 14.0.1. Moreover, this file requires ongoing adjustments because new modules are issued or new folders are created in the system. hgignore becomes excessive: /bitrix/activities/bitrix/
In this case, the folder /bitrix/ cannot be just exempted, because it may contain, among other things, project files: modules, components, website templates, etc. Kernel files are not changed by project developers but come from the "outside" as updates. Technically, it is made by applying a set of rules for the setup file. That is why the kernel is exempted from the version control system. Kernel version on the website server and on the server Copy for developers may differ. Also, we have to make sure whether the changes were made on the "production" website itself and, if necessary, transfer them to the Central repository and to Copies for development. Changes in the "production" website are made from the command line. Then, we push the changes to the Central repository and go to the "Production" website. After the changes have been checked, click Commit and the changes are displayed in the Mercurial environment: The text in red means deletion, in green – addition. Look for the 'ignore' entry in the 'ui' section.
#Tortoisehg global .hgignore how to
See the hgrc (5) man page for details of how to configure these files. In addition, a Mercurial configuration file can reference a set of per-user or global ignore files. A dialog appears which reflects the changes proper and where they were made: Mercurial will ignore file.c if any pattern in. A person responsible for commits uses the command Hg Commit. How Work Is Organizedĭevelopers have changed certain files. Production website - ultimate target of all changes.ĭuring work changes from Copy for development are transferred to the Central repository, and from it to the Production website.Copy for development - workplaces for developers, there may be several workplaces.Central repository is the place where changes are stored.The use of an add-in with a graphic interface is recommended.
#Tortoisehg global .hgignore code
To do so, you can use, for example, Mercurial a cross-platform distributed system of version control developed for efficient work with very big code repositories.
It is not complicated to organize project support by using the version control system if you decide to control only files.
0 kommentar(er)
