<commit_before># Contributing to Thimble


So, you'd like to contribute to Thimble - that's great, we're excited to have you! Thimble is developed by people from all over the world, some just learning to program and others with lots of experience. It's fun and a great way to learn about and advance the open web.

Read through this quick guide for some basic tips. They will help your first contribution go more smoothly.  You can also read [this blog post](http://blog.humphd.org/fixing-a-bug-in-mozilla-thimble/) for a walkthrough of fixing a bug.

### Table of Contents

* [Filing a Bug](#found-a-bug-file-an-issue)
* [Working on your first Issue](#working-on-your-first-issue)

<hr/>

## Found a bug? File an issue
One of the important ways in which you can contribute to Thimble is by filing bug reports when you run into any issues using Thimble.

* **[File an Issue Here](https://github.com/mozilla/thimble.mozilla.org/issues/new)**

**Guidelines**

* Write a descriptive issue title
  * Bad - ``Editor is broken``
  * Good - ``Editor is not responsive after publishing a project``
* Provide a thorough description of the problem
  * What browser and OS are you using?
  * Does the problem happen all of the time?
* Write out a series of steps for reproducing the bug, for example...
  * Step 1) Create a new project
  * Step 2) Add a second HTML file named "broken.html"
  * Step 3) The editor stops responding at this point
* If possible, include a screenshot of what you are seeing
* Check the console in your browser's developer tools
  * If you see any red errors, incliude a screenshot of those as well

## Working on your first Issue
* [Find a Good First Issue](#find-a-good-first-issue)
* [Claim the issue for yourself](#claim-the-issue-for-yourself)
* [Work on your issue](#work-on-your-issue)
* [Keep "tabs" on your indentation](#keep-tabs-on-your-indentation)
* [Get help](#get-help)
* [Submit a Pull Request](#submit-a-pull-request)
* [Check if your Pull Request is good to go](#check-if-your-pull-request-is-good-to-go)


### Get to know both repositories

Thimble it made up of two parts, each with a separate repository. The [Thimble](https://github.com/mozilla/thimble.mozilla.org/) repo has the homepage as well as all of the UI above the actual editor windows. The [Brackets](https://github.com/mozilla/brackets/) repo (aka, 'Bramble' or 'BRAckets in thiMBLE') contains the editor.  We separate the two apps for security reasons, since our Brackets editor allows users to write and then execute random JavaScript.  By hosting these from different origins, we isolate them and keep everything secure.  It makes development a bit harder, but keeps our users safe.

Go ahead and check them out, the README.md file in each repo contains the instructions on how to get your local development environment up and running.

* [Thimble](https://github.com/mozilla/thimble.mozilla.org/)
* [Brackets](https://github.com/mozilla/brackets/)

### Find a good first issue

Now that you've got your environment up and running, look through the issues in each repo to find a good starter issue. We've used the **Good First Bug** label to indicate which issues are a good place to start. Have a look...

* [Thimble - Good First Bugs](https://github.com/mozilla/thimble.mozilla.org/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22)
* [Brackets - Good First Bugs](https://github.com/mozilla/brackets/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+First+Bug%22)

### Claim the issue for yourself

Once you've found a bug that you are interested in working on...

* Scan over the issue comments and check the **Assignees** section on the right-hand side to make sure someone isn't already working on the issue
* Leave a comment indicating that you want to work on the issue
  * We'll assign you and add a **Assigned to Contributor** label
  * This lets everyone know the issue is being worked on and someone won't take it on at the same time
* Take one issue at a time
* If someone has claimed an issue but it seems like they've stopped working on it, leave a comment asking them if it's okay to take over the work
* If you decide to stop working on the issue you took, let us know in the issue
* If you choose an issue with a **brackets** label, your changes need to be made in the [brackets](https://github.com/mozilla/brackets) repository.

### Work on your issue
<commit_msg>Fixed a typo in CONTRIBUTING.md file (#2709)<commit_after># Contributing to Thimble


So, you'd like to contribute to Thimble - that's great, we're excited to have you! Thimble is developed by people from all over the world, some just learning to program and others with lots of experience. It's fun and a great way to learn about and advance the open web.

Read through this quick guide for some basic tips. They will help your first contribution go more smoothly.  You can also read [this blog post](http://blog.humphd.org/fixing-a-bug-in-mozilla-thimble/) for a walkthrough of fixing a bug.

### Table of Contents

* [Filing a Bug](#found-a-bug-file-an-issue)
* [Working on your first Issue](#working-on-your-first-issue)

<hr/>

## Found a bug? File an issue
One of the important ways in which you can contribute to Thimble is by filing bug reports when you run into any issues using Thimble.

* **[File an Issue Here](https://github.com/mozilla/thimble.mozilla.org/issues/new)**

**Guidelines**

* Write a descriptive issue title
  * Bad - ``Editor is broken``
  * Good - ``Editor is not responsive after publishing a project``
* Provide a thorough description of the problem
  * What browser and OS are you using?
  * Does the problem happen all of the time?
* Write out a series of steps for reproducing the bug, for example...
  * Step 1) Create a new project
  * Step 2) Add a second HTML file named "broken.html"
  * Step 3) The editor stops responding at this point
* If possible, include a screenshot of what you are seeing
* Check the console in your browser's developer tools
  * If you see any red errors, incliude a screenshot of those as well

## Working on your first Issue
* [Find a Good First Issue](#find-a-good-first-issue)
* [Claim the issue for yourself](#claim-the-issue-for-yourself)
* [Work on your issue](#work-on-your-issue)
* [Keep "tabs" on your indentation](#keep-tabs-on-your-indentation)
* [Get help](#get-help)
* [Submit a Pull Request](#submit-a-pull-request)
* [Check if your Pull Request is good to go](#check-if-your-pull-request-is-good-to-go)


### Get to know both repositories

Thimble is made up of two parts, each with a separate repository. The [Thimble](https://github.com/mozilla/thimble.mozilla.org/) repo has the homepage as well as all of the UI above the actual editor windows. The [Brackets](https://github.com/mozilla/brackets/) repo (aka, 'Bramble' or 'BRAckets in thiMBLE') contains the editor.  We separate the two apps for security reasons, since our Brackets editor allows users to write and then execute random JavaScript.  By hosting these from different origins, we isolate them and keep everything secure.  It makes development a bit harder, but keeps our users safe.

Go ahead and check them out, the README.md file in each repo contains the instructions on how to get your local development environment up and running.

* [Thimble](https://github.com/mozilla/thimble.mozilla.org/)
* [Brackets](https://github.com/mozilla/brackets/)

### Find a good first issue

Now that you've got your environment up and running, look through the issues in each repo to find a good starter issue. We've used the **Good First Bug** label to indicate which issues are a good place to start. Have a look...

* [Thimble - Good First Bugs](https://github.com/mozilla/thimble.mozilla.org/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22)
* [Brackets - Good First Bugs](https://github.com/mozilla/brackets/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+First+Bug%22)

### Claim the issue for yourself

Once you've found a bug that you are interested in working on...

* Scan over the issue comments and check the **Assignees** section on the right-hand side to make sure someone isn't already working on the issue
* Leave a comment indicating that you want to work on the issue
  * We'll assign you and add a **Assigned to Contributor** label
  * This lets everyone know the issue is being worked on and someone won't take it on at the same time
* Take one issue at a time
* If someone has claimed an issue but it seems like they've stopped working on it, leave a comment asking them if it's okay to take over the work
* If you decide to stop working on the issue you took, let us know in the issue
* If you choose an issue with a **brackets** label, your changes need to be made in the [brackets](https://github.com/mozilla/brackets) repository.

### Work on your issue

{'fraction_non_alphanumeric': 0.08825865002836075, 'fraction_numerical': 0.004310833806012479, 'mean_word_length': 4.210401891252955, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 16, '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': '2432227', 'n_tokens_mistral': 2584, 'n_tokens_neox': 2430, 'n_words': 1228}