![]() ![]() The branch should be pushed to the official repo only when sharing with other people (for collaborative work or review / testing) is needed. The branch for integration of patches or developments based on an obsolete version is created from a relevant tag or commit. The branch for new developments is to be created from the current master. The branch is created by the developer in his local repository when the development of a contribution starts. Possibility to work with other branches can be enabled by the Bugmaster on request. (The full real name can be used as well in this case add the login username in parentheses.)īy default, contributors are allowed to push branches only with the names starting with CR (followed by the relevant Mantis issue ID). This is important to clearly identify the authorship of commits. The name specified in the user.name field in Git configuration should correspond to your login name on the OCCT development portal. Occasionally topic branches with non-standard names can be created by the Bugmaster for special needs.The name can have an additional postfix used if more than one branch was created for the same issue. The topic branches should be named by the pattern "CR12345" where 12345 is the ID of the relevant issue registered in Mantis (without leading zeroes), and "CR" stands for "Change Request". Topic branches created by contributors to submit changes for review / testing or for collaborative development.Official OCCT releases are marked by tags. This branch is updated by the Bugmaster only. The current certified version of OCCT: the "master" branch.URL of the official OCCT source code Git repository (accessed by SSH protocol) is: official repository contains: This and related documents are available at the Resources page of the OCCT development portal at. Please make sure to get familiar with the Contribution Workflow document that describes how Git is used for processing contributions to OCCT. ![]() Many good books on Git can be found at įor the experienced Git users it can be enough to read sections 1 and 3 of this document to start working with the repository. Please consult a book or manual describing Git to get acquainted with this tool. Reading this document does not exempt from the need to learn Git concepts and tools. The purpose of this document is to provide a practical introduction to Git to OCCT developers who are not familiar with this tool and to facilitate the use of the official OCCT Git repository for code contribution to OCCT. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |