<commit_before># Contributing
Contributing to QPixel follows broadly the same process as any other Codidact project.

## What needs doing?
 - **Bugs** are reported here on GitHub. Have a look at the open issues tagged `type: bug` to find something that needs fixing.
 - Any other development work will be listed in the [MVP TODO GitHub project board](https://github.com/codidact/qpixel/projects/2), 
   and will have an issue attached to it.
   
Once you've picked what you're going to work on, please **leave a comment** on the issue to indicate you're planning to work on
it; this helps us reduce wasted effort. If there's not already an issue for the feature you want to work on, please create one.
If you need time to work on an issue, that's absolutely fine, but please **keep us updated** with comments on the issue - if we
don't hear from you for a few weeks, we may assume you've given up working on that issue and give it to someone else.

## What's the workflow?
 * First, **you need an issue to work under**. Either assign yourself to an existing issue (or request it be assigned to you),
   or create a new issue and assign yourself to that.
 * Second, you can make your changes. If you have write access to the repository, create a topic branch (please use the format
   `art/40/add-bells-and-whistles`, i.e. `username/issue-number/brief-description`) and make your changes there; if not, fork
   the repository and work in your fork.
 * Once you've made your changes, submit a pull request targeting the `develop` branch.
<commit_msg>Clarify contributing guidelines<commit_after># Contributing
Contributing to QPixel follows broadly the same process as any other Codidact project.

## What needs doing?
 - **Bugs** are reported here on GitHub. Have a look at the open issues tagged `type: bug` to find something that needs fixing.
 - Any other development work will be listed in the [MVP TODO GitHub project board](https://github.com/codidact/qpixel/projects/2), 
   and will have an issue attached to it.
   
Once you've picked what you're going to work on, please **leave a comment** on the issue to indicate you're planning to work on
it; this helps us reduce wasted effort. If there's not already an issue for the feature you want to work on, please create one.
If you need time to work on an issue, that's absolutely fine, but please **keep us updated** with comments on the issue - if we
don't hear from you for a few weeks, we may assume you've given up working on that issue and give it to someone else.

## What's the workflow?
 * First, **you need an issue to work under**. Look at the current [TODO list](https://github.com/codidact/qpixel/wiki/TODO-list)
   to find something to work on; follow the instructions there to see what's available, and create an issue once you know what you're
   going to work on.
 * Second, you can make your changes. If you have write access to the repository, create a topic branch (please use the format
   `art/40/add-bells-and-whistles`, i.e. `username/issue-number/brief-description`) and make your changes there; if not, fork
   the repository and work in your fork.
 * Once you've made your changes, submit a pull request targeting the `develop` branch.

{'fraction_non_alphanumeric': 0.0689869484151647, 'fraction_numerical': 0.0018645121193287756, 'mean_word_length': 4.006220839813375, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 3, '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': '6764323', 'n_tokens_mistral': 863, 'n_tokens_neox': 824, 'n_words': 501}