hatate 0.1.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eb0a5d94d2de95bec6d613596ad266719f2f20005cdd9912dde0ed9b5521e1a1
-  data.tar.gz: e2658e172844c1617cfb8bd878f475d8fe07d86255def25e25e1275f3209d9bb
+  metadata.gz: 4f58e91d27771d9149b87abe9b3fd3eab68f8199a2c2da19f4623ad04fee3c60
+  data.tar.gz: 772d24b869d0857cc8f052db772822a583d393e66303420dcd4d034586f26f80
 SHA512:
-  metadata.gz: 1ca46b75754aa3b6a416d1900e05e2e18cf34cdd55e514519398903a95a6be75b7822b224ee2b3189e0f926f21b3e4c99915dac066267ee2e4d5bff6f01598a2
-  data.tar.gz: e43c19e1d89910c2306bfb9c6611cfd30c86adae7d5ff8a52288e2136beeb1a13041ccfd521dad45b06c55cee4603fea1d0a02ef1b62ec803e4387e069b897c1
+  metadata.gz: a7514eb04a94b5a4fb57319f191c3d8c97233b9b53e2420ef4d490f1502591e55a73ed50beb2511395eb0a6236738527d68f6a1490e29631253f08c2d47f53b2
+  data.tar.gz: bf2793c96bccc931e5ef9b176a165abc9e145e3cc9901bfc534e9459fbcb123b36f543664f046f37b8e6c72c8ae3e6af45b501cd03066a53548ea7dfc6716978

data/.ruby-version

@@ -0,0 +1 @@
+3.2.2

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 ## [Unreleased]
 
+## [0.2.1] - 2023-05-18
+
+- No changes
+
+## [0.2.0] - 2023-05-18
+
+- Implement basic boilerplate template
+
 ## [0.1.0] - 2023-05-04
 
 - Initial release

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    hatate (0.1.0)
+    hatate (0.2.1)
       rails (~> 7.0.4)
 
 GEM
@@ -110,6 +110,8 @@ GEM
     nio4r (2.5.9)
     nokogiri (1.14.3-arm64-darwin)
       racc (~> 1.4)
+    nokogiri (1.14.3-x86_64-linux)
+      racc (~> 1.4)
     parallel (1.23.0)
     parser (3.2.2.1)
       ast (~> 2.4.1)
@@ -199,6 +201,7 @@ GEM
 
 PLATFORMS
   arm64-darwin-22
+  x86_64-linux
 
 DEPENDENCIES
   hatate!

data/README.md

@@ -3,7 +3,7 @@
 Hatate is an opinionated Ruby on Rails application generator. It makes a whole
 bunch of choices that I like, and I hope you like them too.
 
-## Installation
+## Usage
 
 Install the Hatate gem:
 
@@ -13,29 +13,45 @@ Then run:
 
     hatate new <app_name>
 
-## Usage
+## What's included?
 
-TODO: Write usage instructions here
+- Postgres
+- Tailwind CSS
+- Propshaft
+- Hotwire
+- RSpec
+- FactoryBot
+- Capybara
+- Cuprite
+- Standard
+- GitHub Actions
 
 ## Development
 
-Hatate requires the latest Ruby version
+Hatate requires the latest Ruby version.
+
+Clone the repo, then run:
+
+    bin/setup
+
+Run tests with:
+
+    bundle exec rspec
+
+And run Standard with:
+
+    bundle exec standardrb
 
-After checking out the repo, run `bin/setup` to install dependencies. Then, run
-`rake spec` to run the tests. You can also run `bin/console` for an interactive
-prompt that will allow you to experiment.
+You can step in to a console with:
 
-To install this gem onto your local machine, run `bundle exec rake install`. To
-release a new version, update the version number in `version.rb`, and then run
-`bundle exec rake release`, which will create a git tag for the version, push
-git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+    bin/console
 
-## Contributing
+## Releasing
 
-Bug reports and pull requests are welcome on GitHub at
-https://github.com/cpjmcquillan/hatate. This project is intended to be a safe,
-welcoming space for collaboration, and contributors are expected to adhere to
-the [code of conduct](https://github.com/[USERNAME]/hatate/blob/main/CODE_OF_CONDUCT.md).
+1. Bump the version number in `lib/hatate/version.rb`
+1. Run `bundle exec rake release`, which will create a git tag for the version,
+   push git commits and the created tag, and push the `.gem` file to
+   [rubygems.org](https://rubygems.org).
 
 ## License
 

data/exe/hatate

@@ -1,5 +1,14 @@
 #!/usr/bin/env ruby
 
+require "pathname"
+
+source_path = File.expand_path("#{Pathname.new(__FILE__).dirname}/../lib")
+$LOAD_PATH << source_path
+
 require "hatate"
 
-puts "Hello world!"
+templates_root = File.expand_path(File.join("..", "templates"), File.dirname(__FILE__))
+Hatate::AppGenerator.source_root(templates_root)
+Hatate::AppGenerator.source_paths << Rails::Generators::AppGenerator.source_root << templates_root
+
+Hatate::AppGenerator.start

data/lib/hatate/app_builder.rb

@@ -0,0 +1,69 @@
+module Hatate
+  class AppBuilder < Rails::AppBuilder
+    def readme
+      template "README.md.erb", "README.md"
+    end
+
+    def gemfile
+      template "Gemfile.erb", "Gemfile"
+    end
+
+    def leftovers
+      bundle_command "exec standardrb --fix-unsafely"
+      initial_commit
+    end
+
+    def database_config
+      inject_into_file(
+        "config/database.yml",
+        postgres_test_config,
+        after: "database: #{app_name}_test"
+      )
+    end
+
+    def dependencies
+      bundle_command "install"
+      bundle_command "lock --add-platform x86_64-linux"
+      rails_command "tailwindcss:install"
+    end
+
+    def github_actions
+      template "lint.yml", ".github/workflows/lint.yml"
+      template "test.yml", ".github/workflows/test.yml"
+    end
+
+    def test_helpers
+      template "spec/.rspec", ".rspec"
+      template "spec/spec_helper.rb", "spec/spec_helper.rb"
+      template "spec/rails_helper.rb", "spec/rails_helper.rb"
+      template "spec/support/cuprite.rb", "spec/support/cuprite.rb"
+      template "spec/support/system.rb", "spec/support/system.rb"
+      template "spec/support/factory_bot.rb", "spec/support/factory_bot.rb"
+      template "spec/support/freeze_time.rb", "spec/support/freeze_time.rb"
+      template "spec/support/i18n.rb", "spec/support/i18n.rb"
+    end
+
+    def ruby_version
+      create_file ".ruby-version", "#{Hatate::RUBY_VERSION}\n"
+    end
+
+    private
+
+    def postgres_test_config
+      "
+  host: <%= ENV.fetch(\"POSTGRES_HOST\", \"localhost\") %>
+  username: <%= ENV.fetch(\"POSTGRES_USER\", \"\") %>
+  password: <%= ENV.fetch(\"POSTGRES_PASSWORD\", \"\") %>
+      "
+    end
+
+    def initial_commit
+      git add: "."
+      git commit: "-m 'Initial commit' -m '#{commit_message}'"
+    end
+
+    def commit_message
+      "This app was generated with [hatate](https://github.com/cpjmcquillan/hatate)"
+    end
+  end
+end

data/lib/hatate/app_generator.rb

@@ -0,0 +1,32 @@
+module Hatate
+  class AppGenerator < Rails::Generators::AppGenerator
+    def initialize(*args)
+      super
+
+      self.options = options.merge(
+        database: "postgresql",
+        css: "tailwind",
+        asset_pipeline: "propshaft",
+        skip_test: true,
+        skip_jbuilder: true,
+        skip_bundle: true
+      ).freeze
+    end
+
+    def finish_template
+      build :ruby_version
+      build :dependencies
+      build :database_config
+      build :test_helpers
+      build :github_actions
+
+      super
+    end
+
+    private
+
+    def get_builder_class
+      Hatate::AppBuilder
+    end
+  end
+end

data/lib/hatate/version.rb

@@ -1,6 +1,10 @@
 # frozen_string_literal: true
 
 module Hatate
-  VERSION = "0.1.0"
+  VERSION = "0.2.1"
   RAILS_VERSION = "~> 7.0.4"
+  RUBY_VERSION = IO
+    .read("#{File.dirname(__FILE__)}/../../.ruby-version")
+    .strip
+    .freeze
 end

data/lib/hatate.rb

@@ -1,6 +1,10 @@
 # frozen_string_literal: true
 
-require_relative "hatate/version"
+require "rails/generators/rails/app/app_generator"
+
+require "hatate/version"
+require "hatate/app_generator"
+require "hatate/app_builder"
 
 module Hatate
   class Error < StandardError; end

data/templates/Gemfile.erb

@@ -0,0 +1,44 @@
+source "https://rubygems.org"
+git_source(:github) { |repo| "https://github.com/#{repo}.git" }
+
+ruby "<%= Hatate::RUBY_VERSION %>"
+
+# Rails defaults
+gem "rails", "~> 7.0.4", ">= 7.0.4.3"
+
+## Database
+gem "pg"
+
+## Web server
+gem "puma"
+
+## Asset pipeline
+gem "propshaft"
+gem "importmap-rails"
+gem "tailwindcss-rails"
+
+## Hotwire
+gem "stimulus-rails"
+gem "turbo-rails"
+
+## Other
+gem "bootsnap", require: false
+gem "redis"
+gem "tzinfo-data", platforms: %i[mingw mswin x64_mingw jruby]
+
+group :development do
+  gem "web-console"
+  gem "rack-mini-profiler"
+end
+
+group :development, :test do
+  gem "debug", platforms: %i[mri mingw x64_mingw]
+  gem "factory_bot_rails"
+  gem "rspec-rails"
+  gem "standard"
+end
+
+group :test do
+  gem "capybara"
+  gem "cuprite"
+end

data/templates/README.md.erb

@@ -0,0 +1,34 @@
+# <%= app_name.humanize %>
+
+## Getting started
+
+### Pre-requisites
+
+- Ruby <%= Hatate::RUBY_VERSION %>
+- [postgresql](https://www.postgresql.org)
+
+### Setup
+
+```sh
+bin/setup
+```
+
+## Development
+
+```sh
+bin/dev
+```
+
+## Testing
+
+To run RSpec tests:
+
+```sh
+bundle exec rspec
+```
+
+To run the Standard linter:
+
+```sh
+bundle exec standardrb
+```

data/templates/lint.yml

@@ -0,0 +1,13 @@
+name: Lint
+
+on: push
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          bundler-cache: true
+      - run: bundle exec standardrb

data/templates/spec/.rspec

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

data/templates/spec/rails_helper.rb

@@ -0,0 +1,65 @@
+# This file is copied to spec/ when you run 'rails generate rspec:install'
+require "spec_helper"
+ENV["RAILS_ENV"] ||= "test"
+require_relative "../config/environment"
+# Prevent database truncation if the environment is production
+abort("The Rails environment is running in production mode!") if Rails.env.production?
+require "rspec/rails"
+# Add additional requires below this line. Rails is not loaded until this point!
+require "capybara/rspec"
+
+# Requires supporting ruby files with custom matchers and macros, etc, in
+# spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are
+# run as spec files by default. This means that files in spec/support that end
+# in _spec.rb will both be required and run as specs, causing the specs to be
+# run twice. It is recommended that you do not name files matching this glob to
+# end with _spec.rb. You can configure this pattern with the --pattern
+# option on the command line or in ~/.rspec, .rspec or `.rspec-local`.
+#
+# The following line is provided for convenience purposes. It has the downside
+# of increasing the boot-up time by auto-requiring all files in the support
+# directory. Alternatively, in the individual `*_spec.rb` files, manually
+# require only the support files necessary.
+#
+Dir[Rails.root.join("spec", "support", "**", "*.rb")].sort.each { |f| require f }
+
+# Checks for pending migrations and applies them before tests are run.
+# If you are not using ActiveRecord, you can remove these lines.
+begin
+  ActiveRecord::Migration.maintain_test_schema!
+rescue ActiveRecord::PendingMigrationError => e
+  abort e.to_s.strip
+end
+
+RSpec.configure do |config|
+  # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
+  # config.fixture_path = "#{::Rails.root}/spec/fixtures"
+
+  # If you're not using ActiveRecord, or you'd prefer not to run each of your
+  # examples within a transaction, remove the following line or assign false
+  # instead of true.
+  config.use_transactional_fixtures = true
+
+  # You can uncomment this line to turn off ActiveRecord support entirely.
+  # config.use_active_record = false
+
+  # RSpec Rails can automatically mix in different behaviours to your tests
+  # based on their file location, for example enabling you to call `get` and
+  # `post` in specs under `spec/controllers`.
+  #
+  # You can disable this behaviour by removing the line below, and instead
+  # explicitly tag your specs with their type, e.g.:
+  #
+  #     RSpec.describe UsersController, type: :controller do
+  #       # ...
+  #     end
+  #
+  # The different available types are documented in the features, such as in
+  # https://relishapp.com/rspec/rspec-rails/docs
+  config.infer_spec_type_from_file_location!
+
+  # Filter lines from Rails gems in backtraces.
+  # config.filter_rails_from_backtrace!
+  # arbitrary gems may also be filtered via:
+  # config.filter_gems_from_backtrace("gem name")
+end

data/templates/spec/spec_helper.rb

@@ -0,0 +1,96 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# See https://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+  # The settings below are suggested to provide a good initial experience
+  # with RSpec, but feel free to customize to your heart's content.
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "tmp/.rspec_examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  # https://rspec.info/features/3-12/rspec-core/configuration/zero-monkey-patching-mode/
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = "doc"
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = nil
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+end

data/templates/spec/support/cuprite.rb

@@ -0,0 +1,13 @@
+require "capybara/cuprite"
+
+Capybara.javascript_driver = :cuprite
+
+Capybara.register_driver(:cuprite) do |app|
+  Capybara::Cuprite::Driver.new(
+    app,
+    window_size: [1200, 800],
+    timeout: 10,
+    headless: ENV.fetch("CUPRITE_HEADLESS", true),
+    js_errors: ENV.fetch("CUPRITE_JS_ERRORS", false)
+  )
+end

data/templates/spec/support/factory_bot.rb

@@ -0,0 +1,3 @@
+RSpec.configure do |config|
+  config.include FactoryBot::Syntax::Methods
+end

data/templates/spec/support/freeze_time.rb

@@ -0,0 +1,3 @@
+RSpec.configure do |config|
+  config.include ActiveSupport::Testing::TimeHelpers
+end

data/templates/spec/support/i18n.rb

@@ -0,0 +1,3 @@
+RSpec.configure do |config|
+  config.include ActionView::Helpers::TranslationHelper
+end

data/templates/spec/support/system.rb

@@ -0,0 +1,9 @@
+RSpec.configure do |config|
+  config.before(:each, type: :system) do
+    driven_by :rack_test
+  end
+
+  config.before(:each, type: :system, js: true) do
+    driven_by :cuprite
+  end
+end

data/templates/test.yml

@@ -0,0 +1,36 @@
+name: Test
+
+on: push
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    env:
+      RAILS_ENV: test
+      POSTGRES_HOST: localhost
+      POSTGRES_USER: postgres
+      POSTGRES_PASSWORD: postgres
+
+    services:
+      postgres:
+        image: postgres
+        env:
+          POSTGRES_HOST: localhost
+          POSTGRES_USER: postgres
+          POSTGRES_PASSWORD: postgres
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+
+    steps:
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          bundler-cache: true
+      - run: bin/rails db:prepare
+      - run: bin/rails assets:precompile
+      - run: bundle exec rspec

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: hatate
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Connor McQuillan
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-05-06 00:00:00.000000000 Z
+date: 2023-05-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -35,18 +35,30 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".rspec"
-- ".standard.yml"
+- ".ruby-version"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
 - README.md
 - Rakefile
 - exe/hatate
-- hatate.gemspec
 - lib/hatate.rb
+- lib/hatate/app_builder.rb
+- lib/hatate/app_generator.rb
 - lib/hatate/version.rb
+- templates/Gemfile.erb
+- templates/README.md.erb
+- templates/lint.yml
+- templates/spec/.rspec
+- templates/spec/rails_helper.rb
+- templates/spec/spec_helper.rb
+- templates/spec/support/cuprite.rb
+- templates/spec/support/factory_bot.rb
+- templates/spec/support/freeze_time.rb
+- templates/spec/support/i18n.rb
+- templates/spec/support/system.rb
+- templates/test.yml
 homepage: https://github.com/cpjmcquillan/hatate
 licenses:
 - MIT
@@ -60,9 +72,9 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - "~>"
     - !ruby/object:Gem::Version
-      version: 3.0.0
+      version: 3.2.2
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
@@ -72,5 +84,5 @@ requirements: []
 rubygems_version: 3.4.12
 signing_key:
 specification_version: 4
-summary: Generate a Rails application just how I like it.
+summary: Generate a Rails application with this opinionated generator.
 test_files: []

data/.standard.yml

@@ -1,3 +0,0 @@
-# For available configuration options, see:
-#   https://github.com/testdouble/standard
-ruby_version: 3.0

data/CODE_OF_CONDUCT.md

@@ -1,84 +0,0 @@
-# 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, 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 e-mail 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 me@cpjmcquillan.com. 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.0,
-available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/hatate.gemspec

@@ -1,38 +0,0 @@
-# frozen_string_literal: true
-
-require_relative "lib/hatate/version"
-
-Gem::Specification.new do |spec|
-  spec.name = "hatate"
-  spec.version = Hatate::VERSION
-  spec.authors = ["Connor McQuillan"]
-  spec.email = ["me@cpjmcquillan.com"]
-
-  spec.summary = "Generate a Rails application just how I like it."
-
-  spec.description = <<~HERE
-    Hatate is an opinionated Ruby on Rails application generator. It makes a
-    whole bunch of choices that I like, and I hope you like them too.
-  HERE
-
-  spec.homepage = "https://github.com/cpjmcquillan/hatate"
-  spec.license = "MIT"
-  spec.required_ruby_version = ">= 3.0.0"
-
-  spec.metadata["homepage_uri"] = spec.homepage
-  spec.metadata["source_code_uri"] = spec.homepage
-  spec.metadata["changelog_uri"] = spec.homepage + "/blob/main/CHANGELOG.md"
-
-  # Specify which files should be added to the gem when it is released.
-  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
-  spec.files = Dir.chdir(__dir__) do
-    `git ls-files -z`.split("\x0").reject do |f|
-      (File.expand_path(f) == __FILE__) || f.start_with?(*%w[bin/ test/ spec/ features/ .git .circleci appveyor])
-    end
-  end
-  spec.bindir = "exe"
-  spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
-  spec.require_paths = ["lib"]
-
-  spec.add_dependency "rails", Hatate::RAILS_VERSION
-end