Gale, Maria, Sara, Kimberley - Carets

.github/PULL_REQUEST_TEMPLATE

@@ -4,12 +4,12 @@ Congratulations! You're submitting your assignment! These comprehension question
 ## Comprehension Questions
 | Question | Answer    |
 | :------------- | :------------- |
-| How did your team break up the work to be done? |    |
-| How did your team utilize git to collaborate? |    |
-| What did your group do to try to keep your code DRY while many people collaborated on it?  |    |
-| What was a technical challenge that you faced as a group?  |    |
-| What was a team/personal challenge that you faced as a group?  |    |
-| What could your team have done better?  |    |
-| What was your application's ERD? (include a link) |    |
-| What is your Trello URL? |        |
-| What is the Heroku URL of your deployed application? |        |
+| How did your team break up the work to be done? | We started with assigning people to Trello cards.  the models and controllers for testing and creating the methods. We set up the tasks in waves on Trello and as we completed the tasks, we moved on to different tasks in the waves. |
+| How did your team utilize git to collaborate? | We used to git to work on different branches based on features and tests. We then did a collaborative merge, pull, push after each day's stand up. |
+| What did your group do to try to keep your code DRY while many people collaborated on it?  | We tried switching focus areas, such as products and orders, when we started our testing, that way we were reviewing other team member's models and controllers and would essentially proof each other's code to DRY it up. We also used before actions and custom methods that helped us dry the code up. |
+| What was a technical challenge that you faced as a group?  |  Deploying to Heroku. We had trouble logging in with git and with our database. We reviewed the Heroku logs and StackOverflow to determine the solutions. |
+| What was a team/personal challenge that you faced as a group?  |  We think we did a good job overall with ask and guess culture. It was a challenge having a group member out for 2 days, but as a group, we feel we communicated well over Slack to move forward with the project. |
+| What could your team have done better?  | Deployed earlier to work out those issues.  |
+| What was your application's ERD? (include a link) | We will Slack the photos of the ERD. We did it on the white board as opposed to electronically. |
+| What is your Trello URL? | https://trello.com/b/d42fqbbE/whythehexnots  |
+| What is the Heroku URL of your deployed application? | http://sourceress.herokuapp.com/  |

.gitignore

@@ -0,0 +1,24 @@
+# See https://help.github.com/articles/ignoring-files for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile '~/.gitignore_global'
+
+# Ignore bundler config.
+/.bundle
+
+# Ignore all logfiles and tempfiles.
+/log/*
+/tmp/*
+!/log/.keep
+!/tmp/.keep
+
+/node_modules
+/yarn-error.log
+
+.byebug_history
+.env
+
+public/assets/**
+
+/coverage/

Gemfile

@@ -0,0 +1,77 @@
+source 'https://rubygems.org'
+
+git_source(:github) do |repo_name|
+  repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?("/")
+  "https://github.com/#{repo_name}.git"
+end
+
+gem 'awesome_print'
+gem "paperclip", "~> 5.0.0"
+gem 'omniauth'
+gem 'omniauth-github'
+gem 'simplecov'
+
+# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
+gem 'rails', '~> 5.1.4'
+# Use postgresql as the database for Active Record
+gem 'pg', '~> 0.18'
+# Use Puma as the app server
+gem 'puma', '~> 3.7'
+# Use SCSS for stylesheets
+gem 'sass-rails', '~> 5.0'
+# Use Uglifier as compressor for JavaScript assets
+gem 'uglifier', '>= 1.3.0'
+# See https://github.com/rails/execjs#readme for more supported runtimes
+# gem 'therubyracer', platforms: :ruby
+
+# Use CoffeeScript for .coffee assets and views
+# gem 'coffee-rails', '~> 4.2'
+# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
+gem 'turbolinks', '~> 5'
+# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
+gem 'jbuilder', '~> 2.5'
+# Use Redis adapter to run Action Cable in production
+# gem 'redis', '~> 3.0'
+# Use ActiveModel has_secure_password
+# gem 'bcrypt', '~> 3.1.7'
+
+# Use Capistrano for deployment
+# gem 'capistrano-rails', group: :development
+
+group :development, :test do
+  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
+  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
+  # Adds support for Capybara system testing and selenium driver
+  gem 'capybara', '~> 2.13'
+  gem 'selenium-webdriver'
+  gem 'dotenv-rails'
+  gem 'simplecov'
+  gem 'pry-rails'
+end
+
+group :development do
+  # Access an IRB console on exception pages or by using <%= console %> anywhere in the code.
+  gem 'web-console', '>= 3.3.0'
+  gem 'listen', '>= 3.0.5', '< 3.2'
+  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
+  gem 'spring'
+  gem 'spring-watcher-listen', '~> 2.0.0'
+end
+
+# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
+gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]
+
+gem 'jquery-turbolinks'
+gem 'foundation-rails', '6.4.1.2'
+group :development do
+  gem 'better_errors'
+
+  gem 'binding_of_caller'
+end
+
+group :test do
+  gem 'minitest-rails'
+  gem 'minitest-reporters'
+end
+
+gem 'jquery-rails'