Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions .gitignore

This file was deleted.

51 changes: 51 additions & 0 deletions How to Contribute/Git Setup.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
Installing and Setting Up Git
============

At the heart of GitHub is an open source version control system (VCS) called Git*. Created by the same team that created Linux, Git is responsible for everything GitHub related that happens locally on your computer.

`Download and install the latest version of Git.
<http://git-scm.com/downloads/>`_.

Use the default options for each step.

Setup Git
----------

Now that you have Git installed, it's time to configure your settings. To do this you need to open Git Bash (not the Windows command line).

Git Configuration
----------

**Username**

First you need to tell git your name, so that it can properly label the commits you make.

.. code-block:: bash

git config --global user.name "Your Hame Here"
# Sets the default name for git to use when you commit

**Email**

Git saves your email address into the commits you make. We use the email address to associate your commits with your GitHub account.

.. code-block:: bash

git config --global user.email "your_email@example.com"
# Sets the default email for git to use when you commit

Your email address for Git should be the same one associated with your GitHub account. If it is not, see this guide for help adding additional emails to your GitHub account. If you want to keep your email address hidden, this guide may be useful to you.


Password caching
----------

The last option we need to set will tell git that you don't want to type your username and password every time you talk to a remote server.

Tip: You need git 1.7.10 or newer to use the credential helper To use this option, you need install a credential helper.

GitHub for Windows includes this helper, and provides a git shell so you don't need to install and configure git manually.

If you don't want to use GitHub for Windows, you can download the helper for your OS here:

Windows Vista, 7, & 8 (.NET 4.0 required) Source Unzip the file and run the git-credential-winstore.exe program inside. This will start up the helper and update your git config to use it.
70 changes: 70 additions & 0 deletions How to Contribute/Using Git.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
Using Git to Contribute
============

If you have not already, you need to install and set up Git before you can perform these steps. If you need help with doing that see the Git Setup guide in the contributing folder.

The process you are about to preform is to fork a repository. Which makes a copy of it for your Github account. While SWGANH is open source, we do not allow direct commits. This is so developers can review the accuracy of the code. Accuracy can be a multitude of things, including: It's functionality, It's ability to perform, If it has bugs, or even if it is content is before publish 14.1.

Forking a Repository
----------

To start, you need to fork the repository you want to work with. In this instance we will say it is "swganh", the main server core. Forking adds a copy of the repository to your account. It is the first step in contributing.

.. image:: https://github-images.s3.amazonaws.com/help/Bootcamp-Fork.png

Cloning your Repository
----------

The next step is to clone your repository with Git. This is downloading it to your computer. To do so, run the following code.

.. code-block:: bash

cd C:/Users/your-user-account/where-ever-you-want-your-repository
# Goes to that specified location. That is where your files will get downloaded too.
git clone https://github.com/**your-username**/swganh.git
# Clones your fork of the repository into the current directory in terminal


Committing
----------

After you have changed a file in the source or added some content and you wish to submit it to be reviewed by the Developers, you can make a commit.

.. code-block:: bash

git status
# lists the status of the master. Telling you what files are different from the current public
# repository on github (if you used "cd C:/your-origin-whatever")

Find the files you want to change and type

.. code-block:: bash

git add path-to-file.file-type
# Adds the specified files.

If you alter multiple files and want to commit all of them, you can use:

.. code-block:: bash

git add *

If you delete a file and want it to be completley removed/deleted from the repository when you commit, you can use:

.. code-block:: bash

git rm * (or git rm path-to-file.file-type

Then when you are ready to commit:

.. code-block:: bash
git commit "Added Rebel Themepark"
# Where the "" represents the commit message.


Submitting a Pull Request
----------

When you have a commit, or more than one commit ready to be sent for review you need to submit a "Pull Request" so developers can preview your changes, then approve or decline it. Do that on this page:

https://github.com/anhstudios/swganh/compare
7 changes: 7 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
SWG:ANH Documentation
===========

Welcome to the SWG:ANH Documentation Repository. This repository provides guides, information, and tutorials on using SWG:ANH tools and services.


Browse the various folders to find what you are looking for. If you need help, please do not hesitate to ask on our forums.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.