-
Notifications
You must be signed in to change notification settings - Fork 363
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #786 from nopresearcher/update-documentation
update contributing documents
- Loading branch information
Showing
1 changed file
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -64,14 +64,14 @@ Here's an overview of how you can make a pull request against this project: | |
|
||
1. Fill out the [Splunk Contribution Agreement](https://www.splunk.com/goto/contributions). | ||
2. Fork the [analytic\_story\_execution GitHub repository](https://github.com/splunk/attack_range/issues) | ||
3. Clone your fork using git and create a branch off of master | ||
3. Clone your fork using git and create a branch off of develop | ||
|
||
``` | ||
$ git clone [email protected]:YOUR_GITHUB_USERNAME/attack_range.git | ||
$ cd attack_range | ||
# This project uses 'master' for all development activity, so create your branch off that | ||
$ git checkout -b your-bugfix-branch-name master | ||
# This project uses 'develop' for all development activity, so create your branch off that | ||
$ git checkout -b your-bugfix-branch-name develop | ||
``` | ||
4. Make your changes, commit, and push (once your tests have passed) | ||
|