<commit_before># Contributing

You want to contribute to Pony-msgpack? Awesome.

There are a number of ways to contribute. As this document is a little long, feel free to jump to the section that applies to you currently:

* [Bug report](#bug-report)
* [How to contribute](#how-to-contribute)
* [Pull request](#pull-request)

Additional notes regarding formatting:

* [Documentation formatting](#documentation-formatting)
* [Code formatting](#code-formatting)
* [File Naming](#standard-library-file-naming)

## Bug report

First of all please [search existing issues][https://github.com/SeanTAllen/pony-msgpack/issues] to make sure your issue hasn't already been reported. If you cannot find a suitable issue — [create a new one][https://github.com/SeanTAllen/pony-msgpack/issues/new].

Provide the following details:

  - short summary of what you were trying to achieve,
  - a code snippet causing the bug,
  - expected result,
  - actual results and
  - environment details: at least operating system version

If possible, try to isolate the problem and provide just enough code to demonstrate it. Add any related information which might help to fix the issue.

## How to Contribute

This project uses a fairly standard GitHub pull request workflow. If you have already contributed to a project via GitHub pull request, you can skip this section and proceed to the [specific details of what we ask for in a pull request](#pull-request). If this is your first time contributing to a project via GitHub, read on.

Here is the basic GitHub workflow:

1. Fork this repo. you can do this via the GitHub website. This will result in you having your own copy of the repo under your GitHub account. 
2. Clone your forked repo to your local machine
3. Make a branch for your change
4. Make your change on that branch
5. Push your change to your repo 
6. Use the github ui to open a PR

Some things to note that aren't immediately obvious to folks just starting out:

1. Your fork doesn't automatically stay up to date with changes in the main repo.<commit_msg>Fix incorrect link format in contributing guide<commit_after># Contributing

You want to contribute to Pony-msgpack? Awesome.

There are a number of ways to contribute. As this document is a little long, feel free to jump to the section that applies to you currently:

* [Bug report](#bug-report)
* [How to contribute](#how-to-contribute)
* [Pull request](#pull-request)

Additional notes regarding formatting:

* [Documentation formatting](#documentation-formatting)
* [Code formatting](#code-formatting)
* [File Naming](#standard-library-file-naming)

## Bug report

First of all please [search existing issues](https://github.com/SeanTAllen/pony-msgpack/issues) to make sure your issue hasn't already been reported. If you cannot find a suitable issue — [create a new one](https://github.com/SeanTAllen/pony-msgpack/issues/new).

Provide the following details:

  - short summary of what you were trying to achieve,
  - a code snippet causing the bug,
  - expected result,
  - actual results and
  - environment details: at least operating system version

If possible, try to isolate the problem and provide just enough code to demonstrate it. Add any related information which might help to fix the issue.

## How to Contribute

This project uses a fairly standard GitHub pull request workflow. If you have already contributed to a project via GitHub pull request, you can skip this section and proceed to the [specific details of what we ask for in a pull request](#pull-request). If this is your first time contributing to a project via GitHub, read on.

Here is the basic GitHub workflow:

1. Fork this repo. you can do this via the GitHub website. This will result in you having your own copy of the repo under your GitHub account. 
2. Clone your forked repo to your local machine
3. Make a branch for your change
4. Make your change on that branch
5. Push your change to your repo 
6. Use the github ui to open a PR

Some things to note that aren't immediately obvious to folks just starting out:

1. Your fork doesn't automatically stay up to date with changes in the main repo.
{'fraction_non_alphanumeric': 0.06180589087397392, 'fraction_numerical': 0.003380009657170449, 'mean_word_length': 4.250950570342205, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, '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': '4352192', 'n_tokens_mistral': 1102, 'n_tokens_neox': 1037, 'n_words': 607}