<commit_before># How to write good Bash scripts?

- Use `#!/usr/bin/env bash` instead of `#!/bin/bash` it's [more portable](http://stackoverflow.com/a/21613044).
- Read [this guide](https://github.com/progrium/bashstyle) and follow it. Your scripts will be better.
- Use [shellcheck](https://github.com/koalaman/shellcheck) as a linter.
- Use [beautysh](https://github.com/bemeurer/beautysh) to format your script.
<commit_msg>fix too many new lines<commit_after># How to write good Bash scripts?

- Use `#!/usr/bin/env bash` instead of `#!/bin/bash` it's [more portable](http://stackoverflow.com/a/21613044).
- Read [this guide](https://github.com/progrium/bashstyle) and follow it. Your scripts will be better.
- Use [shellcheck](https://github.com/koalaman/shellcheck) as a linter.
- Use [beautysh](https://github.com/bemeurer/beautysh) to format your script.
{'fraction_non_alphanumeric': 0.15777262180974477, 'fraction_numerical': 0.018561484918793503, 'mean_word_length': 4.462025316455696, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, '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': '5731881', 'n_tokens_mistral': 314, 'n_tokens_neox': 287, 'n_words': 80}