From c68828efd8e68d0fdea2a51e526538f26cb0cb84 Mon Sep 17 00:00:00 2001 From: Neil Dorin Date: Tue, 11 Feb 2020 21:37:51 -0700 Subject: [PATCH] Updated Home (markdown) --- Home.md | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/Home.md b/Home.md index 3044a94..ebcd45c 100644 --- a/Home.md +++ b/Home.md @@ -1 +1,20 @@ -Welcome to the Essentials wiki! +# Welcome to the Essentials Documentation wiki! + +This area is clearly in-progress right now. Take a look at the links to the right. We are actively working on this documentation, so please be patient with us. If you have any comments, reach out to Heath and Neil. + +Thanks! + +# Open Source Collaborative Workflow + +The `master` branch always contain the latest stable version. The `development` branch is used for most development efforts. + +[GitFlow](https://nvie.com/posts/a-successful-git-branching-model/) will be used as the workflow for this collaborative project. To contribute, follow this process: + +1. Fork this repository +2. Create a branch using standard GitFlow branch prefixes (feature/hotfix/bugfix) followed by a descriptive name. + - Example: `feature/add-awesomeness`,`bugfix/wow-im-dumb` or `hotfix/really-big-oops` + - When working on a new feature or bugfix, branch from the `development` branch. When working on a hotfix, branch from `master`. +3. Make commits as necessary (often is better). And use concise, descriptive language, leveraging issue notation and/or [Closing Keywords](https://help.github.com/articles/closing-issues-using-keywords) to ensure any issues addressed by your work are referenced accordingly. +3. When the scope of the work for your branch is complete, make sure to rebase your branch in case further progress has been made since the repo was forked +4. Create a Pull Request to pull your branch into the appropriate branch in the main repository. +5. Your Pull Request will be reviewed by our team and evaluated for inclusion into the main repository. \ No newline at end of file