<commit_before># Contributing

Would you like to contribute? Great! Have a look at [React Native's "getting started" guide](http://facebook.github.io/react-native/docs/getting-started.html) to help you get your computer set up, and make a pull request! (If you feel like you should have write access to the repo, please make an issue and we can discuss it.)

If you are looking to get started with the project, issues tagged with [`good first issue`](https://github.com/StoDevX/AAO-React-Native/issues?q=is%3Aissue+label%3A%22good+first+issue%22+is%3Aopen) are a great place to start. These issues are ones that the team has identified as simple, small changes that won't get too deep, and will be easy to approve for merging.

## Table of Contents
1. [Labels](#labels)
2. [Keep It Running](#keep-it-running)
3. [Maintainers](#maintainers)
4. [CI Notes](#ci-notes)

## Labels
We have a lot of labels! Even though they may seem unorganized, there's a method to the madness.

- <kbd>bug/*</kbd> – These labels relate to the various types of bugs we get: accessibility, layout, and everything else
- <kbd>bugsnag</kbd> – Hardly used. Our in-app crash reporting system can be configured to automatically report crashes with this label, but it's currently disabled
- <kbd>component/*</kbd> – For the "reusable" components in the app: filter, analytics, and markdown
- <kbd>data/*</kbd> – Regarding our various data sources: bus routes, BonApp menus, building hours, and everything else
- <kbd>dep/*</kbd> – Used when reporting bugs to blame either a JS or native dependency
- <kbd>discussion</kbd> – Highlights issues that are in "discussion"
- <kbd>good first issue</kbd> – Highlights anything we've identified as a good way to get your feet wet
- <kbd>help wanted</kbd> – We don't really use it. I guess it's used on PRs when someone needs help? But we usually just mention someone by name instead
- <kbd>platform/*</kbd> – Used to show that a problem/feature request only applies to one platform or the other
- <kbd>pr/*</kbd> – These originate from before Github had their Review system, but it's still helpful for these to stick around, because they let the author of the PR say "okay, this is ready for someone to review" or "this is broken right now"
- <kbd>release-note-worthy</kbd> – Not entirely sure why this exists. I think it's so that we can use it to filter down the PRs that were merged when we write up the release notes?
- <kbd>status/*</kbd> – The different states that an issue or PR can be in: blocked, dup, in progress, on hold(?), or pending an upstream update
- <kbd>tool/*</kbd> – Issues/PRs that affect our various tools: fastlane, CircleCI, Bugsnag, Danger, ESLint, Flow, Gradle, a custom script, or Testflight
- <kbd>triage</kbd> – Automatically applied to issues that are filed without any labels
- <kbd>type/*</kbd>
    - <kbd>type/bugfix</kbd> – used for PRs that fix bugs<commit_msg>CONTRIBUTING: Refactor first and second paragraphs<commit_after># Contributing

Would you like to contribute? Great! Have a look at
[React Native's "getting started" guide][rn-gs] to help you get your
computer set up, and make a pull request! (If you feel like you
should have write access to the repo, please make an issue and we can
discuss it.)

If you are looking to get started with the project, issues tagged with
[`good first issue`][gfi] are a great place to start. These issues are
ones that the team has identified as simple, small changes that won't
get too deep, and will be easy to approve for merging.

[rn-gs]: http://facebook.github.io/react-native/docs/getting-started.html
[gfi]: https://github.com/StoDevX/AAO-React-Native/issues?q=is%3Aissue+label%3A%22good+first+issue%22+is%3Aopen

## Table of Contents
1. [Labels](#labels)
2. [Keep It Running](#keep-it-running)
3. [Maintainers](#maintainers)
4. [CI Notes](#ci-notes)

## Labels
We have a lot of labels! Even though they may seem unorganized, there's a method to the madness.

- <kbd>bug/*</kbd> – These labels relate to the various types of bugs we get: accessibility, layout, and everything else
- <kbd>bugsnag</kbd> – Hardly used. Our in-app crash reporting system can be configured to automatically report crashes with this label, but it's currently disabled
- <kbd>component/*</kbd> – For the "reusable" components in the app: filter, analytics, and markdown
- <kbd>data/*</kbd> – Regarding our various data sources: bus routes, BonApp menus, building hours, and everything else
- <kbd>dep/*</kbd> – Used when reporting bugs to blame either a JS or native dependency
- <kbd>discussion</kbd> – Highlights issues that are in "discussion"
- <kbd>good first issue</kbd> – Highlights anything we've identified as a good way to get your feet wet
- <kbd>help wanted</kbd> – We don't really use it. I guess it's used on PRs when someone needs help? But we usually just mention someone by name instead
- <kbd>platform/*</kbd> – Used to show that a problem/feature request only applies to one platform or the other
- <kbd>pr/*</kbd> – These originate from before Github had their Review system, but it's still helpful for these to stick around, because they let the author of the PR say "okay, this is ready for someone to review" or "this is broken right now"
- <kbd>release-note-worthy</kbd> – Not entirely sure why this exists. I think it's so that we can use it to filter down the PRs that were merged when we write up the release notes?
- <kbd>status/*</kbd> – The different states that an issue or PR can be in: blocked, dup, in progress, on hold(?), or pending an upstream update
- <kbd>tool/*</kbd> – Issues/PRs that affect our various tools: fastlane, CircleCI, Bugsnag, Danger, ESLint, Flow, Gradle, a custom script, or Testflight
- <kbd>triage</kbd> – Automatically applied to issues that are filed without any labels
- <kbd>type/*</kbd>
    - <kbd>type/bugfix</kbd> – used for PRs that fix bugs
{'fraction_non_alphanumeric': 0.09738273283480625, 'fraction_numerical': 0.0037389530931339226, 'mean_word_length': 4.484622553588071, 'pattern_counts': {'":': 0, '<': 67, '<?xml version=': 0, '>': 67, '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': '1148134', 'n_tokens_mistral': 1775, 'n_tokens_neox': 1698, 'n_words': 858}