![]() ![]() However, for GlueX, we treat the remote, "origin," "master" branch of the sim-recon/hdds/etc.There is no inherent definition of a "trunk" in git like there is svn, just a series of branches. By default, the "master" branch is created on your local machine after performing "git clone," but it is not a special or unique branch.In git, branches are simply pointers to different snapshots of the content of the git repository.To create clones of the master repositories into the directories :.Feel free to setup your system up as you see fit of course. This setup isn't required, just my recommendation.This way, you can switch between development projects/branches as needed, keeping them clean and separated from each other, and merge them back to the "master" branch individually when they're ready.Each new code development project (bug fix, feature addition, etc.) should have it's own code development branch in the development clone.The (My) recommended way of doing this is to have a wholly separate clone of the repository for each tagged release, in addition to one clone of the repository used for code development.For example, you may want to have a program running off of a tagged release, and meanwhile develop code separately on a different branch. In general, you probably want to have several separate copies of the repository built simultaneously on your machine.for the entire history of the project into the current, local directory. The "git clone" command pulls all of the code, branches, etc. The first thing you need to do is to create a clone of the master repository on your local machine.git remote set-url origin Additional guidance for setting up GitHub ssh access can be found in the Offline How To.To test your ssh connection try: ssh -T To set your local repository for ssh access do the following (for the example of halld_recon):.Connecting with ssh is the recommended method now, with some overview provided here.Git config -global user.email As of August 2021 password authentication to GitHub was deprecated. Also, be sure to tell git your username and email so that it correctly attributes your commits to you.See Mark's email about how to create an account on GitHub and how to join the "gluex" team on github: Link The GlueX repositories are hosted on GitHub.This document has been distilled from information in the below references.The steps outlined here can be performed in the order as listed to set everything up properly and to use git.Also, some shortcuts/features are skipped so as not to clutter this document. This document is intended to contain the basic information needed for GlueX users and code developers to use git in the GlueX software environment.12.5 Revert to Previous Commit, Deleting Current Workspace Changes.12.4 Cleanup Once Changes Have Been Accepted.12.3 Committing Changes to the Local and Origin Repositories.12.2 Setting up a Code Development Branch.12.1 Getting Started and Checking out Tagged Releases.6 Adding files and/or Committing changes.3 Creating a local clone of the repository. ![]()
0 Comments
Leave a Reply. |