<commit_before># CONTRIBUTING TO THREE.JS

## 1. Index

1. [Index](https://github.com/gero3/three.js/blob/patch-6/CONTRIBUTING.md#2-Index)
2. [Having a problem](https://github.com/gero3/three.js/blob/patch-6/CONTRIBUTING.md#2-having-a-problem)
  * [How to report](https://github.com/gero3/three.js/blob/patch-6/CONTRIBUTING.md#how-to-report)
  * [Migrating problems](https://github.com/gero3/three.js/blob/patch-6/CONTRIBUTING.md#migrating-problems)

## 2. Having a problem

We use 2 different systems to have explain problems.

* [stackoverflow](http://stackoverflow.com/questions/tagged/three.js): This is used when you have a problem in your program. Here we help you out to get further with three.js
* [github issues](https://github.com/mrdoob/three.js/issues): This is used to identify problems and features for three.js itself. This is used by the developers of three.js.

If you are not sure which problem you encountered, then we would like to report it to stackoverflow. For a more extensive explanation, see [issue 1979](https://github.com/mrdoob/three.js/issues/1979).

### How to report.

It's hard to identify a problem without some key parts. What helps??

* Identify the problem. Saying ,It doesn't work, doesn't help much.
* The revision number of three.js
* A small testcase. (Big chance is that when you do this, you'll find the answer yourself.)
* What did you try already??

### Migrating problems. 

Please check our [migrating guide](https://github.com/mrdoob/three.js/wiki/Migration) to be sure that you fixed all problems listed in there. 



<commit_msg>use relative path to create the index<commit_after># CONTRIBUTING TO THREE.JS

## 1. Index

1. [Index](#2-Index)
2. [Having a problem](#2-having-a-problem)
  * [How to report](#how-to-report)
  * [Migrating problems](#migrating-problems)

## 2. Having a problem

We use 2 different systems to have explain problems.

* [stackoverflow](http://stackoverflow.com/questions/tagged/three.js): This is used when you have a problem in your program. Here we help you out to get further with three.js
* [github issues](https://github.com/mrdoob/three.js/issues): This is used to identify problems and features for three.js itself. This is used by the developers of three.js.

If you are not sure which problem you encountered, then we would like to report it to stackoverflow. For a more extensive explanation, see [issue 1979](https://github.com/mrdoob/three.js/issues/1979).

### How to report.

It's hard to identify a problem without some key parts. What helps??

* Identify the problem. Saying ,It doesn't work, doesn't help much.
* The revision number of three.js
* A small testcase. (Big chance is that when you do this, you'll find the answer yourself.)
* What did you try already??

### Migrating problems. 

Please check our [migrating guide](https://github.com/mrdoob/three.js/wiki/Migration) to be sure that you fixed all problems listed in there. 




{'fraction_non_alphanumeric': 0.10866666666666666, 'fraction_numerical': 0.012666666666666666, 'mean_word_length': 3.7111459968602825, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, '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': '2171723', 'n_tokens_mistral': 973, 'n_tokens_neox': 887, 'n_words': 342}