<commit_before># Contributing to the RGSoC Teams App

* Introduction, thanks for contributing
* [Code of Conduct](https://github.com/rails-girls-summer-of-code/rgsoc-teams/blob/master/CODE_OF_CONDUCT.md)

## Reporting a bug

* Very valuable
* Check if issue already exists

## Suggesting a new feature

### Labels

* Dibs
* Ping via comment and/or join Slack

## Creating a Pull Request
(inspired by [jbuilder](https://github.com/rails/jbuilder/blob/master/CONTRIBUTING.md))


* If related to an issue: better ask first
* Fork repo
* Install locally (see [README](https://github.com/rails-girls-summer-of-code/rgsoc-teams/blob/master/README.md) for hints)
* Make sure tests pass locally: `rake spec`

### Create a Topic Branch

Make sure your fork is up-to-date and create a topic branch for your feature or bug fix.

```
git checkout master
git pull upstream master
git checkout -b my-feature-branch
```

### Write Code

* [Ruby Style Guide](https://github.com/bbatsov/ruby-style-guide)
* With tests (TODO: can be hard for beginners)
* Commits w/ descript

### Make a Pull Request

* Point to GH docs?<commit_msg>Add 3rd way of contributing: resolve existing issue<commit_after># Contributing to the RGSoC Teams App

* Introduction, thanks for contributing
* [Code of Conduct](https://github.com/rails-girls-summer-of-code/rgsoc-teams/blob/master/CODE_OF_CONDUCT.md)

## Reporting a bug

* Very valuable
* Check if issue already exists
* Provide as many details as possible (screenshot)

## Suggesting a new feature

### Labels

* Dibs
* Ping via comment and/or join Slack

## Resolving an existing issue

### Finding an issue

* See [`beginner-friendly`](https://github.com/rails-girls-summer-of-code/rgsoc-teams/issues?q=is%3Aissue+is%3Aopen+label%3Abeginner-friendly) issues for your first steps in open source
* See [`#pairwithme`](https://github.com/rails-girls-summer-of-code/rgsoc-teams/labels/%23pairwithme) for more involving issues
* Make sure no one else is already working on it (assignee, comments)
* Check if issue is still valid (comments)

## Creating a Pull Request
(inspired by [jbuilder](https://github.com/rails/jbuilder/blob/master/CONTRIBUTING.md))


* If related to an issue: better ask first
* Fork repo
* Install locally (see [README](https://github.com/rails-girls-summer-of-code/rgsoc-teams/blob/master/README.md) for hints)
* Make sure tests pass locally: `rake spec`

### Create a Topic Branch

Make sure your fork is up-to-date and create a topic branch for your feature or bug fix.

```
git checkout master
git pull upstream master
git checkout -b my-feature-branch
```

### Write Code

* [Ruby Style Guide](https://github.com/bbatsov/ruby-style-guide)
* With tests (TODO: can be hard for beginners)
* Commits w/ descript

### Make a Pull Request

* Point to GH docs?
{'fraction_non_alphanumeric': 0.1143265451947124, 'fraction_numerical': 0.0021436227224008574, 'mean_word_length': 4.426356589147287, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, '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': '4689451', 'n_tokens_mistral': 948, 'n_tokens_neox': 889, 'n_words': 299}