Skip to content

rafopar/epics

This branch is 688 commits ahead of, 2 commits behind boiarino17/epics:master.

Folders and files

NameName
Last commit message
Last commit date
Apr 14, 2015
Jun 6, 2014
Apr 14, 2015
Jun 6, 2014
Jun 6, 2014
Feb 10, 2016
Mar 12, 2015
Mar 4, 2015
Jun 2, 2014
Mar 12, 2015
Apr 14, 2015
Mar 4, 2015
Nov 4, 2014
Dec 15, 2014
Apr 14, 2015

Repository files navigation

#HPS EPICS

Getting Started

To get a github repository setup for HPS EPICS developement:

  • Create a github account and login
  • Create a new repository using the "+" near the top right of the webpage, don't check "Initialize Repository with a README"
  • On your desktop:
mkdir <newdir>
cd <newdir>
git init
git remote add origin https://github.com/<username>/<new-repo-name>
git remote add hps-epics https://github.com/wmoore28/epics
git pull hps-epics master
git push -u origin master
  • Edit/add files then commit the changes. Push to your remote repository (on github).
git add <changed files>
git commit -m "Meaningful comments about changes"
git push

Submit code to HPS EPICS

I recommend doing a pull from the wmoore28/epics first, getting updates from others (See: Staying in sync)

On github, navigate to your repository with the changes you want to submit.

  • Switch to the branch with the changes
  • Click the Compare, review, create a pull request button
  • Ensure the branches being compared are correct and review changes (submit to wmoore28/epics:develop)
  • Click Create pull request

Staying in sync

Add a remote to the official repository (view remotes with 'git remote -v')

git remote add hps-epics https://github.com/wmoore28/epics
# get updates from remote branch, most likely master or develop
git pull hps-epics master
# if everything looks good...push changes to your repo
git push origin master

Using branches

If doing much of a feature add or rework, use a branch.

# Clone your repo.  Example:
git clone https://github.com/wmoore28/epics.git <local-dir>  # defaults to epics
cd <local-dir>
git checkout -b <branch-name>    # omit -b if using an existing branch

Edit/add code then commit the changes. Once ready, push changes to your remote branch (on github).

git add <changed files>
git commit -m "Meaningful comments about changes"
git push origin <branch-name>

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • C++ 42.6%
  • HTML 38.7%
  • C 7.0%
  • Makefile 3.7%
  • Perl 1.8%
  • SourcePawn 1.5%
  • Other 4.7%