<commit_before>Patch submission guidelines [1]_
--------------------------------

We strongly prefer to receive contributions as Github Pull Requests (PR), and that
is what's described below.

If for some reason that is inconvenient, you can generate a patch [2]_ and
send it attached to the mailing list.

Just in case, a `good guide to git <http://documentup.com/skwp/git-workflows-book>`.

Steps
-----

**Make sure there is an open issue for your change.**

Perhaps, if it's a new feature, you probably want to
`discuss it first <http://groups.google.com/group/cocos-discuss>`_

**Have a local clone with upload rights to work with.**

  - if you have commit rights in cocos2d/cocos2d-python, have a clone of that project
  - if you don't, fork the project ( the button 'fork' in https://github.com/los-cocos/cocos ) and then clone ``your-username/cocos2d-python`` project

**Create a new Git branch specific to your change(s).**

For example, if you're adding a new feature to foo the bars, do something 
like the following::

    $ git checkout master
    $ git pull
    $ git checkout -b foo-the-bars
    <hack hack hack>
    $ git push origin HEAD

This makes life much easier for maintainers if you have (or ever plan to
have) additional changes in your own ``master`` branch.

**Submit pull request based on your new 'foo-the-bars' branch.**

  - Go to the Github page associated with your clone; if you forked it is the page for
    ``your-username/cocos2d-python`` project
  - In the button-dropdown list ``branch: zzz`` select branch ``foo-the-bar``<commit_msg>updated some more references to cocos project<commit_after>Patch submission guidelines [1]_
--------------------------------

We strongly prefer to receive contributions as Github Pull Requests (PR), and that
is what's described below.

If for some reason that is inconvenient, you can generate a patch [2]_ and
send it attached to the mailing list.

Just in case, a `good guide to git <http://documentup.com/skwp/git-workflows-book>`.

Steps
-----

**Make sure there is an open issue for your change.**

Perhaps, if it's a new feature, you probably want to
`discuss it first <http://groups.google.com/group/cocos-discuss>`_

**Have a local clone with upload rights to work with.**

  - if you have commit rights in los-cocos/cocos, have a clone of that project
  - if you don't, fork the project ( the button 'fork' in https://github.com/los-cocos/cocos ) and then clone ``your-username/cocos`` project

**Create a new Git branch specific to your change(s).**

For example, if you're adding a new feature to foo the bars, do something 
like the following::

    $ git checkout master
    $ git pull
    $ git checkout -b foo-the-bars
    <hack hack hack>
    $ git push origin HEAD

This makes life much easier for maintainers if you have (or ever plan to
have) additional changes in your own ``master`` branch.

**Submit pull request based on your new 'foo-the-bars' branch.**

  - Go to the Github page associated with your clone; if you forked it is the page for
    ``your-username/cocos`` project
  - In the button-dropdown list ``branch: zzz`` select branch ``foo-the-bar``
{'fraction_non_alphanumeric': 0.10973675864256265, 'fraction_numerical': 0.002537266095781795, 'mean_word_length': 3.3623789764868603, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 2, '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': '4463503', 'n_tokens_mistral': 927, 'n_tokens_neox': 873, 'n_words': 437}