<commit_before># gitGeneral Workflow

1. Clone down the master directly (do not fork):

  -> git clone masterURL yourdirectory

2. Create a new feature branch from master, If it's a new feature, name the branch "featureDescription". If it's a bug fix, name the branch "bugFixDescription".

  -> git checkout -b featureDescription  OR  -> git checkout -b bugFixDescription

3. Make changes and stage them for a commit to your feature branch.

  -> git add -p

4. Commit changes (see commit message guidelines below)  

  -> git commit -m 'message'

5. Ensure your remote master is up to date:

  -> git checkout master
  -> git pull

6. Go back to your feature branch:

  -> git checkout branchname

7. Sync up with latest master before pushing to remote feature branch:

  -> git pull --rebase origin master

8. Fix any merge conflicts if necessary.

9. Push changes to remote feature branch:

  -> git push origin branchname

10. Generate pull request on GitHub:

  ensure base: master
  ensure compare: branchname

11. Fix any issues highlighted by reviewer if necessary.

12. When everything checks out, reviewer merges pull request to master.

13. When a pull request is merged and closed, delete branchname branch.



## Detailed Workflow

### Cut a namespaced feature branch from master

Your branch should follow this naming convention:
  - bugFix/Description
  - feature/Description
  - doc/Description
  - refactor/Description

These commands will help you do this:

# Creates your branch and brings you there

git checkout -b `your-branch-name`

### Make commits to your feature branch.

Prefix each commit like so
  - (feat) Added a new feature
  - (fix) Fixed inconsistent tests [Fixes #0]
  - (refactor) ...
  - (cleanup) ...
  - (test) ...
  - (doc) ...

Make changes and commits on your branch, and make sure that you
only make changes that are relevant to this branch. If you find
yourself making unrelated changes, make a new branch for those
changes.

#### Commit Message Guidelines

- Commit messages should be written in the present tense; e.g. "Fix continuous
  integration script".
- The first line of your commit message should be a brief summary of what the
  commit changes. Aim for about 70 characters max. Remember: This is a summary,
  not a detailed description of everything that changed.
- If you want to explain the commit in more depth, following the first line should
  be a blank line and then a more detailed description of the commit. This can be<commit_msg>Contributing Guidelines Updated for Waffie<commit_after># gitGeneral Workflow

1. Clone down the master directly (do not fork):

  -> git clone masterURL yourdirectory

2. Create a new feature branch from master, If it's a new feature, name the branch "featureDescription". If it's a bug fix, name the branch "bugFixDescription".

  -> git checkout -b featureDescription  OR  -> git checkout -b bugFixDescription

3. Make changes and stage them for a commit to your feature branch.

  -> git add -p

4. Commit changes (see commit message guidelines below)  

  -> git commit -m 'message'

5. Ensure your remote master is up to date:

  -> git checkout master
  -> git pull

6. Go back to your feature branch:

  -> git checkout branchname

7. Sync up with latest master before pushing to remote feature branch:

  -> git pull --rebase origin master

8. Fix any merge conflicts if necessary.

9. Push changes to remote feature branch:

  -> git push origin branchname

10. Generate pull request on GitHub:

  ensure base: master
  ensure compare: branchname

11. Fix any issues highlighted by reviewer if necessary.

12. When everything checks out, reviewer merges pull request to master.

13. When a pull request is merged and closed, delete branchname branch.



## Detailed Workflow

### Cut a namespaced feature branch from master

Your branch should follow this naming convention:
  - #[issue#]-bugFix/Description
  - #[issue#]-feature/Description
  - #[issue#]-doc/Description
  - #[issue#]-refactor/Description

These commands will help you do this:

# Creates your branch and brings you there

git checkout -b `your-branch-name`

### Make commits to your feature branch.

Prefix each commit like so
  - (feat) Added a new feature
  - (fix) Fixed inconsistent tests [Fixes #0]
  - (refactor) ...
  - (cleanup) ...
  - (test) ...
  - (doc) ...

Make changes and commits on your branch, and make sure that you
only make changes that are relevant to this branch. If you find
yourself making unrelated changes, make a new branch for those
changes.

#### Commit Message Guidelines

- Commit messages should be written in the present tense; e.g. "Fix continuous
  integration script".
- The first line of your commit message should be a brief summary of what the
  commit changes. Aim for about 70 characters max. Remember: This is a summary,
  not a detailed description of everything that changed.
- If you want to explain the commit in more depth, following the first line should
  be a blank line and then a more detailed description of the commit. This can be
{'fraction_non_alphanumeric': 0.06602095275746195, 'fraction_numerical': 0.007906700929037358, 'mean_word_length': 3.458149779735683, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 23, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1846342', 'n_tokens_mistral': 1374, 'n_tokens_neox': 1312, 'n_words': 733}