<commit_before># Workflow for submitting Questions, Issues and PRs

* [Asking a Question](#asking-a-question)
* [Posting an Issue](#posting-an-issue)
* [Submitting a PR](#submitting-a-pr)

## Asking a Question

Post your question in the issue tracker.<br>
See [Posting an Issue](#posting-an-issue) for guidelines to follow when posting an issue.

If you don't get an answer within 1-2 days, feel free to post another comment in the issue thread as a reminder.


## Posting an Issue

1. Do a search in the issue tracker to ensure the same issue has not been posted before.
1. Follow the [naming convention](FormatsAndConventions.md#issue) for the issue title. 


## Submitting a PR

> This is an adaptation of the [_GitHub Flow_](https://guides.github.com/introduction/flow/). 

Note that each project might specify additional things to do. i.e. follow these steps in conjunction with 
additional details provided by the specific project.

1. Read any instructions the project has for new contributors. 
   Ensure you have completed orientation activities (if any) prescribed by the project. 

1. Set up the project. These are the typical steps.
   1. Fork the repo to your GitHub account. 
   1. Clone the code to your computer.
   1. Follow the 'Set up guide' provided by the project to set up the project in your computer. 
   1. Ensure the set up is correct by getting all the tests to pass.

1. Select an open issue from the issue tracker that you want to work on. 
   
   > If the issue list does not contain what you want to work on, post an issue (as described [above](#posting-an-issue))
   > and wait for it to get acknowledged. Otherwise you could end up fixing something that does not need fixing.

1. You are recommended to start with an issue specifically marked for first time contributors (i.e. issues with the 
   `d.firstTimers` label). Note that you **should not do more than one `d.firstTimers` label**.
   
   * It is not required to (but OK to) ask for permission to work on an issue. 
   But do check the issue discussion thread to see if there are _active_ PRs for that issue. 
   If someone is already working on that issue, perhaps your efforts are better spent on a different issue.<commit_msg>Add note on license for PRs<commit_after># Workflow for submitting Questions, Issues and PRs

* [Asking a Question](#asking-a-question)
* [Posting an Issue](#posting-an-issue)
* [Submitting a PR](#submitting-a-pr)

## Asking a Question

Post your question in the issue tracker.<br>
See [Posting an Issue](#posting-an-issue) for guidelines to follow when posting an issue.

If you don't get an answer within 1-2 days, feel free to post another comment in the issue thread as a reminder.


## Posting an Issue

1. Do a search in the issue tracker to ensure the same issue has not been posted before.
1. Follow the [naming convention](FormatsAndConventions.md#issue) for the issue title. 


## Submitting a PR

> This is an adaptation of the [_GitHub Flow_](https://guides.github.com/introduction/flow/). 

Note that each project might specify additional things to do. i.e. follow these steps in conjunction with 
additional details provided by the specific project.

IMPORTANT: By submitting a PR, you agree to allow the project owner to license your work under the same 
license as that used by the project.

1. Read any instructions the project has for new contributors. 
   Ensure you have completed orientation activities (if any) prescribed by the project. 

1. Set up the project. These are the typical steps.
   1. Fork the repo to your GitHub account. 
   1. Clone the code to your computer.
   1. Follow the 'Set up guide' provided by the project to set up the project in your computer. 
   1. Ensure the set up is correct by getting all the tests to pass.

1. Select an open issue from the issue tracker that you want to work on. 
   
   > If the issue list does not contain what you want to work on, post an issue (as described [above](#posting-an-issue))
   > and wait for it to get acknowledged. Otherwise you could end up fixing something that does not need fixing.

1. You are recommended to start with an issue specifically marked for first time contributors (i.e. issues with the 
   `d.firstTimers` label). Note that you **should not do more than one `d.firstTimers` label**.
   
   * It is not required to (but OK to) ask for permission to work on an issue. 
   But do check the issue discussion thread to see if there are _active_ PRs for that issue. 
   If someone is already working on that issue, perhaps your efforts are better spent on a different issue.
{'fraction_non_alphanumeric': 0.05982162279747662, 'fraction_numerical': 0.005220796171416141, 'mean_word_length': 3.6585612968591694, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 11, 'https://': 2, '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': '1278465', 'n_tokens_mistral': 1265, 'n_tokens_neox': 1198, 'n_words': 712}