sports-manager 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: c758d344e9f382f5f1490e5a561b9985bac567cab55277644a0ae48374150f43
+  data.tar.gz: 1e8f37239ca689cb3103112a868ec9add0e1b7e95f7fb14a291a80a70b2e856d
+SHA512:
+  metadata.gz: 2d27aa5f4eb1b3ca85708b9f15139a73e31c5fabd35a47396caf7a59c51cfd0f04bb948d86f7cd57aa70de9436634f091472d75b6354b7e4946b895b4d980458
+  data.tar.gz: 742a411241704d99cbe9b4d6410ccf5a4d5dbb829a96210eac778dc9105ba31c0e1adafbe6308d05e257f50fef2ee0c4fccd5d0db222ec4fb43ead9545f87778

data/.rspec

@@ -0,0 +1 @@
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,32 @@
+AllCops:
+  TargetRubyVersion: 2.5
+  NewCops: enable
+  SuggestExtensions: false
+Metrics/BlockLength:
+  Exclude:
+    - spec/**/*.rb
+Metrics/ClassLength:
+  Max: 200
+Metrics/MethodLength:
+  Max: 20
+Layout/FirstArrayElementIndentation:
+  EnforcedStyle: consistent
+Layout/FirstHashElementIndentation:
+  EnforcedStyle: consistent
+Layout/HashAlignment:
+  EnforcedLastArgumentHashStyle: always_inspect
+Layout/MultilineMethodCallIndentation:
+  EnforcedStyle: indented
+Style/Documentation:
+  Enabled: false
+Layout/EndAlignment:
+  EnforcedStyleAlignWith: variable
+Style/ObjectThen:
+  EnforcedStyle: yield_self
+Naming/FileName:
+  Exclude:
+    - 'lib/sports-manager.rb'
+Style/OpenStructUse:
+  Enabled: false
+Gemspec/RequireMFA:
+  Enabled: false

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+devs@rebase.com.br.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/CONTRIBUTING.md

@@ -0,0 +1,72 @@
+# Contributing
+
+Thank you for your interest in contributing! We welcome contributions of all kinds, including new features, bug fixes, and documentation improvements.
+
+Please take a moment to review this document to make the contribution process easy and effective for everyone involved.
+
+If you have any questions, feel free to reach out by opening an issue or contacting the maintainers directly.
+
+## Table of Contents
+1. [How to Report an Issue](#how-to-report-an-issue)
+2. [Submitting a Pull Request](#submitting-a-pull-request)
+3. [Coding Guidelines](#coding-guidelines)
+4. [Code of Conduct](#code-of-conduct)
+
+## How to Report an Issue
+
+If you encounter any bugs or have feature requests, please create an issue on our GitHub repository.
+
+1. Go to the [Issues]((githubrepo)/issues) page.
+2. Click on "New Issue".
+3. Select the "Bug report" or "Feature request".
+4. Fill in the details as prompted by the template.
+
+If your issue does not fit the provided templates, feel free to create an issue without following them. Provide as much detail as possible to help us understand and address your concern.
+
+## Submitting a Pull Request
+To submit a pull request, please follow these steps:
+
+1. **Fork the Repository**:
+    - Navigate to the [repository]((githubrepo)).
+    - Click the "Fork" button in the top-right corner.
+2. **Clone the Forked Repository**:
+    ```sh
+    git clone (githubrepo)
+    cd sports-manager
+    ```
+3. **Create a Branch**:
+    ```sh
+    git checkout -b <your-branch-name>
+    ```
+4. **Make Your Changes**:
+    - Implement your feature, bug fix, or documentation improvement.
+    - If you're making changes to the code, write some tests.
+    - Ensure your code follows our [Coding Guidelines](#coding-guidelines).
+5. **Commit Your Changes**:
+    ```sh
+    git add .
+    git commit -m "Description of your changes"
+    ```
+6. **Push to Your Fork**:
+    ```sh
+    git push origin your-branch-name
+    ```
+7. **Create a Pull Request**:
+    - Go to your fork on GitHub.
+    - Click on the "Compare & pull request" button.
+    - Fill in the details of your pull request and submit.
+
+We will review your pull request and provide feedback. Please be responsive to our comments and make the necessary adjustments.
+
+## Coding Guidelines
+
+To ensure consistency and maintainability of the codebase, please adhere to the following guidelines:
+
+- Follow the Ruby community's [style guide](https://rubystyle.guide/).
+- Write tests for your changes.
+- Ensure all tests pass before submitting a pull request.
+- Document public methods and classes.
+
+## Code of Conduct
+
+By participating in this project, you agree to abide by our [Code of Conduct](./CODE_OF_CONDUCT.md). Please be respectful and considerate in all interactions.

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2024 Rebase, André Benjamim, Gustavo Alberto.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,419 @@
+# Sports Manager Gem
+
+The `sports-manager` gem is a powerful tool designed to generate and manage tournament schedules. It handles complex scheduling tasks, considering various constraints such as court availability, game length, rest breaks, and participant availability. Under the hood, it leverages the [`csp-resolver`](https://github.com/Rebase-BR/csp-resolver) gem to solve these complex Constraint Satisfaction Problems (CSPs).
+
+## Getting Started
+
+### Requirements
+
+- Ruby >= 2.5.8
+
+### Installing
+
+You can install using the following command:
+
+```bash
+gem install "sports-manager"
+```
+
+Then install it:
+
+```bash
+$ bundle install
+```
+
+## Usage
+
+### Setting Up a Tournament
+
+To set up a tournament, you need to provide the following information:
+
+```ruby
+require 'sports-manager'
+
+days = {
+  '2023-09-09': { start: 9, end: 20 },
+  '2023-09-10': { start: 9, end: 13 }
+}
+
+courts = 2
+game_length = 60
+rest_break = 30
+single_day_matches = false
+subscriptions = {
+  mens_single: [
+    { id: 1, name: 'João' },      { id: 2, name: 'Marcelo' },
+    { id: 3, name: 'José' },      { id: 4, name: 'Pedro' },
+    { id: 5, name: 'Carlos' },    { id: 6, name: 'Leandro' },
+    { id: 7, name: 'Leonardo' },  { id: 8, name: 'Cláudio' },
+    { id: 9, name: 'Alexandre' }, { id: 10, name: 'Daniel' },
+    { id: 11, name: 'Marcos' },   { id: 12, name: 'Henrique' },
+    { id: 13, name: 'Joaquim' },  { id: 14, name: 'Alex' },
+    { id: 15, name: 'Bruno' },    { id: 16, name: 'Fábio' }
+  ]
+}
+matches = {
+  mens_single: [
+    [1, 16],
+    [2, 15],
+    [3, 14],
+    [4, 13],
+    [5, 12],
+    [6, 11],
+    [7, 10],
+    [8, 9]
+  ]
+}
+
+solution = SportsManager::TournamentGenerator.new(format: :cli)
+  .add_days(days)
+  .add_courts(courts)
+  .add_game_length(game_length)
+  .add_rest_break(rest_break)
+  .enable_single_day_matches(single_day_matches)
+  .add_subscriptions(subscriptions)
+  .single_elimination_algorithm
+  .add_matches(matches)
+```
+
+You can also pass already generated matches to the generator,
+it's useful when your already have the matches generated by another system, 
+but you still want to generate the schedule.
+
+```ruby
+params = {
+  when: {
+    '2023-09-09': { start: 9, end: 20 },
+    '2023-09-10': { start: 9, end: 13 }
+  },
+  courts: 2,
+  game_length: 60,
+  rest_brake: 30,
+  single_day_matches: false,
+  subscriptions: {
+    mens_single: [
+      { id: 1, name: 'João' },      { id: 2, name: 'Marcelo' },
+      { id: 3, name: 'José' },      { id: 4, name: 'Pedro' },
+      { id: 5, name: 'Carlos' },    { id: 6, name: 'Leandro' },
+      { id: 7, name: 'Leonardo' },  { id: 8, name: 'Cláudio' },
+      { id: 9, name: 'Alexandre' }, { id: 10, name: 'Daniel' },
+      { id: 11, name: 'Marcos' },   { id: 12, name: 'Henrique' },
+      { id: 13, name: 'Joaquim' },  { id: 14, name: 'Alex' },
+      { id: 15, name: 'Bruno' },    { id: 16, name: 'Fábio' }
+    ]
+  },
+  matches: {
+    mens_single: [
+      { id: 1, participants: [1, 16], },
+      { id: 2, participants: [2, 15], },
+      { id: 3, participants: [3, 14], },
+      { id: 4, participants: [4, 13], },
+      { id: 5, participants: [5, 12], },
+      { id: 6, participants: [6, 11], },
+      { id: 7, participants: [7, 10], },
+      { id: 8, participants: [8, 9], },
+      { id: 9, depends_on: [1, 2], round: 1 },
+      { id: 10, depends_on: [3, 4], round: 1 },
+      { id: 11, depends_on: [5, 6], round: 1 },
+      { id: 12, depends_on: [7, 8], round: 1 },
+      { id: 13, depends_on: [9, 10], round: 2 },
+      { id: 14, depends_on: [11, 12], round: 2},
+      { id: 15, depends_on: [13, 14],  round: 2},
+    ]
+  }
+}
+```
+
+#### Configuration methods
+
+- `add_days(days)`: Adds the tournament days.
+- `add_day(day, start, end)`: Adds a single tournament day.
+- `add_courts(courts)`: Adds the number of available courts.
+- `add_game_length(game_length)`: Adds the duration of each game in minutes.
+- `add_rest_break(rest_break)`: Adds the rest time between player matches in minutes.
+- `enable_single_day_matches(single_day_matches)`: Sets if all matches should be on the same day.
+- `add_subscriptions(subscriptions)`: Adds the players or teams participating in each category.
+- `add_subscription(category, subscription)`: Adds a single player or team to a category.
+- `add_subscriptions_per_category(subscriptions_per_category)`: Adds the players or teams participating per category.
+- `add_matches(matches)`: Adds the first matchups for each category.
+- `add_match(category, match)`: Adds a single match to a category.
+- `add_matches_per_category(category, matches_per_category)`: Adds the first matchups per category.
+- `single_elimination_algorithm`: Sets the single elimination algorithm(this option is already default).
+
+
+### Running Example Tournaments
+
+The gem comes with predefined example tournaments:
+
+```ruby
+solution = SportsManager::TournamentGenerator.example(:simple)
+solution = SportsManager::TournamentGenerator.example(:complex)
+#complete, minimal, ...
+```
+
+### Output Formats
+
+You can choose different output formats:
+
+```ruby
+# CLI format (default)
+SportsManager::TournamentGenerator.new(format: :cli)
+
+# Mermaid format (for visual diagrams)
+SportsManager::TournamentGenerator.new(format: :mermaid)
+```
+#### Output examples
+
+```ruby
+require 'sports-manager'
+
+days = {
+  '2023-09-09': { start: 9, end: 20 },
+  '2023-09-10': { start: 9, end: 13 }
+}
+
+courts = 2
+game_length = 60
+rest_break = 30
+single_day_matches = false
+subscriptions = {
+  mens_single: [
+    { id: 1, name: 'João' },      { id: 2, name: 'Marcelo' },
+    { id: 3, name: 'José' },      { id: 4, name: 'Pedro' },
+    { id: 5, name: 'Carlos' },    { id: 6, name: 'Leandro' },
+    { id: 7, name: 'Leonardo' },  { id: 8, name: 'Cláudio' },
+    { id: 9, name: 'Alexandre' }, { id: 10, name: 'Daniel' },
+    { id: 11, name: 'Marcos' },   { id: 12, name: 'Henrique' },
+    { id: 13, name: 'Joaquim' },  { id: 14, name: 'Alex' },
+    { id: 15, name: 'Bruno' },    { id: 16, name: 'Fábio' }
+  ]
+}
+matches = {
+  mens_single: [
+    [1, 16],
+    [2, 15],
+    [3, 14],
+    [4, 13],
+    [5, 12],
+    [6, 11],
+    [7, 10],
+    [8, 9]
+  ]
+}
+
+ solution = SportsManager::TournamentGenerator.new(format: :cli)
+  .add_days(days)
+  .add_courts(courts)
+  .add_game_length(game_length)
+  .add_rest_break(rest_break)
+  .enable_single_day_matches(single_day_matches)
+  .add_subscriptions(subscriptions)
+  .single_elimination_algorithm
+  .add_matches(matches)
+  .call
+```
+```bash
+Tournament Timetable:
+
+Solution 1
+ category   | id | round |     participants      | court |      time     
+------------|----|-------|-----------------------|-------|---------------
+mens_single | 1  | 0     | João vs. Fábio        | 0     | 09/09 at 09:00
+mens_single | 2  | 0     | Marcelo vs. Bruno     | 1     | 09/09 at 09:00
+mens_single | 3  | 0     | José vs. Alex         | 0     | 09/09 at 10:00
+mens_single | 4  | 0     | Pedro vs. Joaquim     | 1     | 09/09 at 10:00
+mens_single | 5  | 0     | Carlos vs. Henrique   | 0     | 09/09 at 11:00
+mens_single | 6  | 0     | Leandro vs. Marcos    | 1     | 09/09 at 11:00
+mens_single | 7  | 0     | Leonardo vs. Daniel   | 0     | 09/09 at 12:00
+mens_single | 8  | 0     | Cláudio vs. Alexandre | 1     | 09/09 at 12:00
+mens_single | 9  | 1     | M1 vs. M2             | 0     | 09/09 at 13:00
+mens_single | 10 | 1     | M3 vs. M4             | 1     | 09/09 at 13:00
+mens_single | 11 | 1     | M5 vs. M6             | 0     | 09/09 at 14:00
+mens_single | 12 | 1     | M7 vs. M8             | 1     | 09/09 at 14:00
+mens_single | 13 | 2     | M9 vs. M10            | 0     | 09/09 at 15:00
+mens_single | 14 | 2     | M11 vs. M12           | 1     | 09/09 at 15:30
+mens_single | 15 | 2     | M13 vs. M14           | 0     | 09/09 at 17:00
+
+Total solutions: 1
+```
+```ruby
+require 'sports-manager'
+
+days = {
+  '2023-09-09': { start: 9, end: 20 },
+  '2023-09-10': { start: 9, end: 13 }
+}
+
+courts = 2
+game_length = 60
+rest_break = 30
+single_day_matches = false
+subscriptions = {
+  mens_single: [
+    { id: 1, name: 'João' },      { id: 2, name: 'Marcelo' },
+    { id: 3, name: 'José' },      { id: 4, name: 'Pedro' },
+    { id: 5, name: 'Carlos' },    { id: 6, name: 'Leandro' },
+    { id: 7, name: 'Leonardo' },  { id: 8, name: 'Cláudio' },
+    { id: 9, name: 'Alexandre' }, { id: 10, name: 'Daniel' },
+    { id: 11, name: 'Marcos' },   { id: 12, name: 'Henrique' },
+    { id: 13, name: 'Joaquim' },  { id: 14, name: 'Alex' },
+    { id: 15, name: 'Bruno' },    { id: 16, name: 'Fábio' }
+  ]
+}
+matches = {
+  mens_single: [
+    [1, 16],
+    [2, 15],
+    [3, 14],
+    [4, 13],
+    [5, 12],
+    [6, 11],
+    [7, 10],
+    [8, 9]
+  ]
+}
+
+ solution = SportsManager::TournamentGenerator.new(format: :mermaid)
+  .add_days(days)
+  .add_courts(courts)
+  .add_game_length(game_length)
+  .add_rest_break(rest_break)
+  .enable_single_day_matches(single_day_matches)
+  .add_subscriptions(subscriptions)
+  .single_elimination_algorithm
+  .add_matches(matches)
+  .call
+```
+```bash
+Solutions:
+--------------------------------------------------------------------------------
+Solutions 1
+Gantt:
+---
+displayMode: compact
+---
+gantt
+  title Tournament Schedule
+  dateFormat DD/MM HH:mm
+  axisFormat %H:%M
+  tickInterval 1hour
+
+  section 0
+    MS M1: 09/09 09:00, 1h
+    MS M3: 09/09 10:00, 1h
+    MS M5: 09/09 11:00, 1h
+    MS M7: 09/09 12:00, 1h
+    MS M9: 09/09 13:00, 1h
+    MS M11: 09/09 14:00, 1h
+    MS M13: 09/09 15:00, 1h
+    MS M15: 09/09 17:00, 1h
+  section 1
+    MS M2: 09/09 09:00, 1h
+    MS M4: 09/09 10:00, 1h
+    MS M6: 09/09 11:00, 1h
+    MS M8: 09/09 12:00, 1h
+    MS M10: 09/09 13:00, 1h
+    MS M12: 09/09 14:00, 1h
+    MS M14: 09/09 15:30, 1h
+Graph:
+graph LR
+classDef court0 fill:#A9F9A9, color:#000000
+classDef court1 fill:#4FF7DE, color:#000000
+subgraph colorscheme
+  direction LR
+
+  COURT0:::court0
+  COURT1:::court1
+end
+subgraph mens_single
+  direction LR
+
+  mens_single_1[1\nJoão vs. Fábio\n09/09 09:00]:::court0
+  mens_single_2[2\nMarcelo vs. Bruno\n09/09 09:00]:::court1
+  mens_single_3[3\nJosé vs. Alex\n09/09 10:00]:::court0
+  mens_single_4[4\nPedro vs. Joaquim\n09/09 10:00]:::court1
+  mens_single_5[5\nCarlos vs. Henrique\n09/09 11:00]:::court0
+  mens_single_6[6\nLeandro vs. Marcos\n09/09 11:00]:::court1
+  mens_single_7[7\nLeonardo vs. Daniel\n09/09 12:00]:::court0
+  mens_single_8[8\nCláudio vs. Alexandre\n09/09 12:00]:::court1
+  mens_single_9[9\nM1 vs. M2\n09/09 13:00]:::court0
+  mens_single_10[10\nM3 vs. M4\n09/09 13:00]:::court1
+  mens_single_11[11\nM5 vs. M6\n09/09 14:00]:::court0
+  mens_single_12[12\nM7 vs. M8\n09/09 14:00]:::court1
+  mens_single_13[13\nM9 vs. M10\n09/09 15:00]:::court0
+  mens_single_14[14\nM11 vs. M12\n09/09 15:30]:::court1
+  mens_single_15[15\nM13 vs. M14\n09/09 17:00]:::court0
+  mens_single_1 --> mens_single_9
+  mens_single_2 --> mens_single_9
+  mens_single_3 --> mens_single_10
+  mens_single_4 --> mens_single_10
+  mens_single_5 --> mens_single_11
+  mens_single_6 --> mens_single_11
+  mens_single_7 --> mens_single_12
+  mens_single_8 --> mens_single_12
+  mens_single_9 --> mens_single_13
+  mens_single_10 --> mens_single_13
+  mens_single_11 --> mens_single_14
+  mens_single_12 --> mens_single_14
+  mens_single_13 --> mens_single_15
+  mens_single_14 --> mens_single_15
+end
+--------------------------------------------------------------------------------
+Total solutions: 1
+```
+```mermaid
+graph LR
+classDef court0 fill:#A9F9A9, color:#000000
+classDef court1 fill:#4FF7DE, color:#000000
+subgraph colorscheme
+  direction LR
+
+  COURT0:::court0
+  COURT1:::court1
+end
+subgraph mens_single
+  direction LR
+
+  mens_single_1[1\nJoão vs. Fábio\n09/09 09:00]:::court0
+  mens_single_2[2\nMarcelo vs. Bruno\n09/09 09:00]:::court1
+  mens_single_3[3\nJosé vs. Alex\n09/09 10:00]:::court0
+  mens_single_4[4\nPedro vs. Joaquim\n09/09 10:00]:::court1
+  mens_single_5[5\nCarlos vs. Henrique\n09/09 11:00]:::court0
+  mens_single_6[6\nLeandro vs. Marcos\n09/09 11:00]:::court1
+  mens_single_7[7\nLeonardo vs. Daniel\n09/09 12:00]:::court0
+  mens_single_8[8\nCláudio vs. Alexandre\n09/09 12:00]:::court1
+  mens_single_9[9\nM1 vs. M2\n09/09 13:00]:::court0
+  mens_single_10[10\nM3 vs. M4\n09/09 13:00]:::court1
+  mens_single_11[11\nM5 vs. M6\n09/09 14:00]:::court0
+  mens_single_12[12\nM7 vs. M8\n09/09 14:00]:::court1
+  mens_single_13[13\nM9 vs. M10\n09/09 15:00]:::court0
+  mens_single_14[14\nM11 vs. M12\n09/09 15:30]:::court1
+  mens_single_15[15\nM13 vs. M14\n09/09 17:00]:::court0
+  mens_single_1 --> mens_single_9
+  mens_single_2 --> mens_single_9
+  mens_single_3 --> mens_single_10
+  mens_single_4 --> mens_single_10
+  mens_single_5 --> mens_single_11
+  mens_single_6 --> mens_single_11
+  mens_single_7 --> mens_single_12
+  mens_single_8 --> mens_single_12
+  mens_single_9 --> mens_single_13
+  mens_single_10 --> mens_single_13
+  mens_single_11 --> mens_single_14
+  mens_single_12 --> mens_single_14
+  mens_single_13 --> mens_single_15
+  mens_single_14 --> mens_single_15
+end
+```
+
+## Contributing
+
+See our [CONTRIBUTING](./CONTRIBUTING.md) guidelines.
+
+## Code of Conduct
+
+We expect that everyone participating in any way with this project follows our [Code of Conduct](./CODE_OF_CONDUCT.md).
+
+## License
+
+This project is licensed under the [MIT License](MIT-LICENSE).

data/Rakefile

@@ -0,0 +1,4 @@
+# frozen_string_literal: true
+
+require 'bundler/gem_tasks'
+task default: %i[]