<commit_before>
### GitHub Issues Import ###

This Python script allows you to import issues and pull requests from one repository to another (works even if the two repositories are not related to each other).

Fork of one of the tools by [<NAME>](https://github.com/mkorenkov) separated from its original location at [`mokorenkov/tools`](https://github.com/mkorenkov/tools).

#### Usage ####

Rename `config.ini.sample` to `config.ini`, and edit the fields to match your login info and repository info. **Warning:** The password is stored in plaintext, so avoid storing the config file in a public repository.
 
Run the script with the following command to import all issues into the repository defined in the config:

```
 $ python3 gh-issues-import.py
```

Or to only import some issues, run the script and include the issue numbers of all issues you wish to import (can be done for one or several issues):

```
 $ python3 gh-issues-import.py 25 26 29
```

#### Result ####

Every issue imported will create a new issue in the target repository. Remember that the ID of the issue in the new repository will most likely not be the same as the ID of the original issue. Keep this in mind when writing commit messages such as _"Closes #25"_.<commit_msg>Include additional argument usage in the README<commit_after>
### GitHub Issues Import ###

This Python script allows you to import issues and pull requests from one repository to another (works even if the two repositories are not related to each other).

Fork of one of the tools by [<NAME>](https://github.com/mkorenkov) separated from its original location at [`mokorenkov/tools`](https://github.com/mkorenkov/tools).

#### Usage ####

Rename `config.ini.sample` to `config.ini`, and edit the fields to match your login info and repository info. Store the config file in the same folder as the `gh-issues-import.py` script, or store it in a different folder, using the `--config <file>` option to specify which config file to load in.

**Warning:** The password is stored in plaintext, so avoid storing the config file in a public repository. To avoid this, you can instead pass the username and/or password as arguments by using the `-u <username>` and `-p <password>` flags respectively.
 
Run the script with the following command to import all open issues into the repository defined in the config:

```
 $ python3 gh-issues-import.py
```

Or to only import some issues, run the script and include the issue numbers of all issues you wish to import (can be done for one or several issues, and will even include closed issues):

```
 $ python3 gh-issues-import.py 25 26 29
```

Some config options can be passed as arguments. For a full list, run the script using the `--help` flag.

#### Result ####

Every issue imported will create a new issue in the target repository. Remember that the ID of the issue in the new repository will most likely not be the same as the ID of the original issue. Keep this in mind when writing commit messages such as _"Closes #25"_.
{'fraction_non_alphanumeric': 0.07768595041322314, 'fraction_numerical': 0.006611570247933884, 'mean_word_length': 4.2717770034843205, 'pattern_counts': {'":': 0, '<': 8, '<?xml version=': 0, '>': 8, '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': '7599115', 'n_tokens_mistral': 786, 'n_tokens_neox': 746, 'n_words': 456}