Pass simplecov

.gitignore

@@ -0,0 +1 @@
+coverage/*

Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+gem 'rspec'
+gem 'simplecov', require: false, group: :test

Gemfile.lock

@@ -0,0 +1,35 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    diff-lcs (1.5.0)
+    docile (1.4.0)
+    rspec (3.12.0)
+      rspec-core (~> 3.12.0)
+      rspec-expectations (~> 3.12.0)
+      rspec-mocks (~> 3.12.0)
+    rspec-core (3.12.2)
+      rspec-support (~> 3.12.0)
+    rspec-expectations (3.12.3)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-mocks (3.12.6)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-support (3.12.1)
+    simplecov (0.22.0)
+      docile (~> 1.1)
+      simplecov-html (~> 0.11)
+      simplecov_json_formatter (~> 0.1)
+    simplecov-html (0.12.3)
+    simplecov_json_formatter (0.1.4)
+
+PLATFORMS
+  arm64-darwin-22
+  arm64-darwin-23
+
+DEPENDENCIES
+  rspec
+  simplecov
+
+BUNDLED WITH
+   2.3.26

README.md

@@ -1,3 +1,41 @@
 # Futbol
 
+https://docs.google.com/spreadsheets/d/1v6x85L1qvHk5-tpt0FHqZrO9v1LS5NdLgFO1EKb3h8s/edit#gid=95404790
+
 Starter repository for the [Turing School](https://turing.io/) Futbol project.
+
+1. A 1-2 summary or bullet points outlining your plan for check-ins throughout the duration of the project.
+- We will meet again on Thursday and Sunday
+- We will have daily Slack commucation.
+- 
+2. A 2-4 sentence summary of your plan for project organization and workflow. This can include bullet points. If you plan to use a project management tool, please include a link to your project board.
+- We will make sure to write the excel sheet first, followed by the test methods, followed by the code, followed by merging.
+- If we do with our code should not have to touch each other at all because we will be all on the same page without having to directly compare non-spec code.
+- Co-author commiting
+- 
+3. A 2-3 sentence summary describing the different approaches your group discussed for project organization and how you collectively made a decision on which to use.
+- Meg made a sick excel sheet that we will be orgainzingn our variables and methods on.
+- Filling in the Excel before working on code will prevent overlap.
+- 
+4. A 2-3 sentence summary describing your approach to the code design.
+- Red-green refractor / Test then code
+- Start with main class and then branch and refactor as appropriate
+- 
+5. https://docs.google.com/document/d/1wf68IH416i1gRNfD4sSy5lah6JwIewbjMIYLxEsAAMo/edit
+- 
+6. Create a section in your README called “Contributors”. List each group member’s name and link to their LinkedIn and Github profiles.
+- Quin Nordmark
+- https://github.com/n0rdie
+- https://www.linkedin.com/in/quin-nordmark-28642b101/
+- 
+- Meg Roth
+- https://github.com/megroth2
+- https://www.linkedin.com/in/meg-roth/
+- 
+- Steven Nash
+- https://github.com/s2an
+- https://www.linkedin.com/in/stephen-nash-557b16111/
+- 
+- Logan Finnegan
+- https://github.com/LoganFinnegan
+- https://www.linkedin.com/in/logan-finnegan-4728461ab/

coverage/.last_run.json

@@ -0,0 +1,5 @@
+{
+  "result": {
+    "line": 100.0
+  }
+}