*Deprecated* This material is for historical purposes only See https://wiki.duraspace.org/display/VIVODOC/All+Documentation for current documentation
*Deprecated* See https://wiki.duraspace.org/display/VIVODOC/All+Documentation for current documentation
Unless you are a core VIVO developer, you cannot commit code directly to the VIVO repositories. Instead, you can contribute using the fork, branch, and pull model. Helpful descriptions of the process are available here or here and the basic steps are described below.
This guide assumes you have already have a GitHub account and have set up git on your local machine.
On your local machine, navigate to a convenient directory in your command line interface
Clone your forked VIVO repository. The https clone url is located on the right side of the GitHub page.
git clone https://github.com/{your_github_username}/VIVO.git
Git will download the project files into a folder named VIVO and start tracking changes. If you will be contributing again in the future, you likely want to set up your local repository to fetch code updates from the main upstream VIVO repository (not covered in this tutorial).
Using branches is a good idea so code changes you make are isolated from each other and can be integrated into the main code repository in separate pull requests.
If you haven't already, switch into the VIVO directory
cd VIVO
Create a new branch, replacing 'myFeature' with a descriptive branch name
git checkout -b myFeature
Tell GitHub about your new branch
git push origin myFeature
Make changes, hack away. Push your commits on your feature branch to the remote repository (your VIVO fork). As an example, I've changed robots.txt and pushed a commit to my fork.
cd productMods nano robots.txt /*edit and save*/ git add robots.txt git commit -m "adjust robots.txt" git push
This is where you ask the core developers to 'pull' your code changes into the main VIVO repository.
Welcome to the VIVO commit history and contributors list!