<commit_before>Submit a new issue only if you are sure it is a missing feature or a bug. Otherwise, [discuss the topic](http://graphhopper.com/#developers) first. 
For new translations or fixes to existing translations,
please refer to [this documentation](https://github.com/graphhopper/graphhopper/blob/master/docs/core/translations.md).

Issues for newcomers are tagged with 
['good first issue'](https://github.com/graphhopper/graphhopper/labels/good%20first%20issue) 
and documentation issues are tagged with 
['documentation'](https://github.com/graphhopper/graphhopper/labels/documentation).

## We love pull requests. Here's a quick guide:

1. [Fork the repo](https://help.github.com/articles/fork-a-repo) and create a branch for your new feature or bug fix.

2. Run the tests. We only take pull requests with passing tests: `mvn clean test verify`

3. Add at least one test for your change. Only refactoring and documentation changes
require no new tests. Also make sure you submit a change specific to exactly one issue. If you have ideas for multiple 
changes please create separate pull requests.

4. Make the test(s) pass.

5. Push to your fork and [submit a pull request](https://help.github.com/articles/using-pull-requests). A button should
appear on your fork its github page afterwards.

## License Agreement

For contributions like pull requests, bug fixes and translations please read and electronically sign 
the <a href="http://www.clahub.com/agreements/graphhopper/graphhopper">GraphHopper License Agreement</a>,
which gives not away your rights but it will make sure for others that you agree to the Apache License, Version 2.

## Syntax:<commit_msg>CLAhub is not reliable anymore, switch to manual or signaturit.com process in contributing guide lines, also add a code of conduct<commit_after>Submit a new issue only if you are sure it is a missing feature or a bug. Otherwise, [discuss the topic](http://graphhopper.com/#developers) first. 
For new translations or fixes to existing translations,
please refer to [this documentation](https://github.com/graphhopper/graphhopper/blob/master/docs/core/translations.md).

Issues for newcomers are tagged with 
['good first issue'](https://github.com/graphhopper/graphhopper/labels/good%20first%20issue) 
and documentation issues are tagged with 
['documentation'](https://github.com/graphhopper/graphhopper/labels/documentation).

## We love pull requests. Here's a quick guide:

1. [Fork the repo](https://help.github.com/articles/fork-a-repo) and create a branch for your new feature or bug fix.

2. Run the tests. We only take pull requests with passing tests: `mvn clean test verify`

3. Add at least one test for your change. Only refactoring and documentation changes
require no new tests. Also make sure you submit a change specific to exactly one issue. If you have ideas for multiple 
changes please create separate pull requests.

4. Make the test(s) pass.

5. Push to your fork and [submit a pull request](https://help.github.com/articles/using-pull-requests). A button should
appear on your fork its github page afterwards.

## License Agreement

For contributions like pull requests, bug fixes and translations please read 
the <a href="https://graphhopper.com/agreements/individual-cla.html">GraphHopper License Agreement</a>, which includes our
<a href="https://graphhopper.com/agreements/cccoc.html">contributor covenant code of conduct</a>.
<a href="https://graphhopper.com/#contact">Send us</a> an email with the signed print out of it OR a request to do 
this via signaturit.com which is simpler and faster but requires storing your Email there.
Our CLA does not influence your rights on your contribution but it makes sure for others that you agree to the Apache License, Version 2.
After this you'll appear in the <a href="CONTRIBUTORS.md">contributors list</a> and you pull request can be also technically discussed.

## Syntax:
{'fraction_non_alphanumeric': 0.08312085670576237, 'fraction_numerical': 0.005099439061703213, 'mean_word_length': 4.727007299270073, 'pattern_counts': {'":': 0, '<': 13, '<?xml version=': 0, '>': 13, 'https://': 13, 'lorem ipsum': 0, 'www.': 1, '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': '6562001', 'n_tokens_mistral': 1091, 'n_tokens_neox': 1031, 'n_words': 481}