lolcommits 0.17.3 → 0.18.0

data/CODE_OF_CONDUCT.md

@@ -1,71 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-education, socio-economic status, nationality, personal appearance, race,
-religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers 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, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Reporting
-
-If you are subject to or witness unacceptable behavior, or have any other
-concerns, please notify a project maintainer. All reports will be kept
-confidential and will be reviewed and investigated promptly.
-
-We will investigate every complaint and take appropriate action. We reserve the
-right to remove any content that violates this Code of Conduct, or to
-temporarily or permanently ban any contributor for other behaviors that we deem
-inappropriate, threatening, offensive, or harmful.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org

data/CONTRIBUTING.md

@@ -1,44 +0,0 @@
-### Contributing
-
-Pull Requests are welcome! To start helping out on lolcommits:
-
-[Fork](https://guides.github.com/activities/forking/) then clone the repository:
-
-    git clone git@github.com:your-username/lolcommits.git
-
-Create your feature branch:
-
-    git checkout -b my-new-feature
-
-When you are happy with your change, run the full test suite:
-
-    bundle exec rake
-
-Please ensure nothing is broken. It'd be awesome if you manually tested for
-regressions as well (since the test suite is far from complete).
-
-This default rake task uses [RuboCop](https://github.com/bbatsov/rubocop) to
-ensure Ruby style guidelines. If you want to run tests before conforming to this
-to verify functionality, just run `rake test` and `rake features` manually.
-
-With a passing test suite, commit your changes, push and submit a new [Pull
-Request](https://github.com/lolcommits/lolcommits/compare/):
-
-    git commit -am 'Added some feature'
-    git push origin my-new-feature
-
-At this point you'll be waiting for one of our maintainers to review it. We will
-try to reply to new Pull Requests within a few days. We might suggest some
-changes, improvements or alternatives. To increase the chance that your pull
-request gets accepted:
-
-* Explain what your are doing (and why) in your Pull Request description.
-* If you are fixing an
-  [issue](https://github.com/lolcommits/lolcommits/issues), link to
-  it in your description and [mention
-  it](https://help.github.com/articles/closing-issues-via-commit-messages/) in
-  the commit message.
-* Write a good [commit
-  message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
-* Write tests.
-

data/Gemfile

@@ -1,6 +0,0 @@
-source "https://rubygems.org"
-git_source(:github) { |repo| "https://github.com/#{repo}.git" }
-
-gemspec
-
-gem "cucumber", github: "cucumber/cucumber-ruby", ref: "a468bc6"

data/PULL_REQUEST_TEMPLATE.md

@@ -1,16 +0,0 @@
-
-Explain what you're changing and why here.
-
----
-#### :memo: Checklist
-
-Please check this list and leave it intact for the reviewer. Thanks! :heart:
-
-- [ ] Commit messages provide context (why not just what, some tips [here](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)).
-- [ ] If relevant, mention GitHub issue number above and include in a commit message.
-- [ ] Latest code from master merged.
-- [ ] New behaviour has test coverage.
-- [ ] Avoid duplicating code.
-- [ ] No commented out code.
-- [ ] Avoid comments for your code, write code that explains itself.
-- [ ] Changes are simple, useful, clear and brief.

data/Rakefile

@@ -1,16 +0,0 @@
-require "bundler/setup"
-require "bundler/gem_tasks"
-
-require "minitest/test_task"
-Minitest::TestTask.create(:test) do |t|
-  t.warning = false
-end
-
-require "rdoc/task"
-Rake::RDocTask.new do |rdoc|
-  rdoc.main = "README.md"
-  rdoc.rdoc_files.include("README.md", "lib/**/*.rb", "bin/**/*")
-  rdoc.rdoc_dir = "doc"
-end
-
-task default: :test

data/bin/cucumber

@@ -1,25 +0,0 @@
-#!/usr/bin/env ruby
-#
-# This file was generated by Bundler.
-#
-# The application 'cucumber' is installed as part of a gem, and
-# this file is here to facilitate running it.
-#
-
-ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../Gemfile", __dir__)
-
-bundle_binstub = File.expand_path("bundle", __dir__)
-
-if File.file?(bundle_binstub)
-  if File.read(bundle_binstub, 300).include?("This file was generated by Bundler")
-    load(bundle_binstub)
-  else
-    abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
-Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
-  end
-end
-
-require "rubygems"
-require "bundler/setup"
-
-load Gem.bin_path("cucumber", "cucumber")

data/bin/rubocop

@@ -1,25 +0,0 @@
-#!/usr/bin/env ruby
-#
-# This file was generated by Bundler.
-#
-# The application 'rubocop' is installed as part of a gem, and
-# this file is here to facilitate running it.
-#
-
-ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../Gemfile", __dir__)
-
-bundle_binstub = File.expand_path("bundle", __dir__)
-
-if File.file?(bundle_binstub)
-  if File.read(bundle_binstub, 300).include?("This file was generated by Bundler")
-    load(bundle_binstub)
-  else
-    abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
-Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
-  end
-end
-
-require "rubygems"
-require "bundler/setup"
-
-load Gem.bin_path("rubocop", "rubocop")

data/features/bugs.feature

@@ -1,52 +0,0 @@
-Feature: Bug regression testing
-  As a developer
-  I want to ensure fixed bugs stay fixed
-  So that I don't have to fix them again!
-
-  Background:
-    Given a mocked home directory
-
-  #
-  # issue #58, https://github.com/lolcommits/lolcommits/issues/58
-  #
-  Scenario: handle git repos with spaces in directory name
-    Given I am in a git repo named "test lolol" with lolcommits enabled
-    And I run `git commit --allow-empty -m 'can haz commit'`
-    Then the output should contain "*** Preserving this moment in history."
-    And a directory named "../.lolcommits/test-lolol" should exist
-
-  #
-  # issue #68, https://github.com/lolcommits/lolcommits/issues/68
-  #
-  @fake-interactive-rebase @slow_process
-  Scenario: Don't trigger capture during a git rebase
-    Given I am in a git repo named "yuh8history" with lolcommits enabled
-      And I do 2 git commits
-    When I run `git rebase -i HEAD~2`
-    Then there should be exactly 2 jpgs in "~/.lolcommits/yuh8history"
-
-  #
-  # issue #87, https://github.com/lolcommits/lolcommits/issues/87
-  #
-  @fake-no-imagemagick
-  Scenario: gracefully fail when imagemagick is not installed
-    When I run `lolcommits`
-    Then the output should contain:
-      """
-      ImageMagick does not appear to be properly installed
-      """
-    And the exit status should be 1
-
-  #
-  # issue #50, https://github.com/lolcommits/lolcommits/issues/50
-  #
-  Scenario: catch upstream bug with ruby-git and color=always
-    Given I am in a git repo named "whatev" with lolcommits enabled
-    And I run `git config color.ui always`
-    When I run `lolcommits`
-    Then the output should contain:
-      """
-      Due to a bug in the ruby-git library, git config for color.ui cannot be set to 'always'.
-      """
-    And the output should contain "Try setting it to 'auto' instead!"
-    And the exit status should be 1

data/features/lolcommits.feature

@@ -1,376 +0,0 @@
-Feature: Basic UI functionality
-
-  Background:
-    Given a mocked home directory
-
-  Scenario: App just runs
-    When I get help for "lolcommits"
-    Then the exit status should be 0
-    And the banner should be present
-
-  Scenario: Shows version information
-    When I run `lolcommits --version`
-    Then the output should show the version number
-    And the exit status should be 0
-
-  Scenario: Help should show the animate option on a Mac platform
-    Given I am using a "darwin" platform
-    When I get help for "lolcommits"
-    Then the following options should be documented:
-      | --animate | which is optional |
-      | -a        | which is optional |
-
-  Scenario: Help should not show the animate option on a Windows plaftorm
-    Given I am using a "win32" platform
-    When I get help for "lolcommits"
-    Then the output should not match /\-a\, \-\-animate\=SECONDS/
-
-  Scenario: Enable in a naked git repo
-    Given I am in a git repo
-    When I run `lolcommits --enable`
-    Then the output should contain "installed lolcommit hook to:"
-      And the lolcommits git post-commit hook should be properly installed
-      And the exit status should be 0
-
-  Scenario: Enable in a git repo that already has a git post-commit hook
-    Given I am in a git repo
-    And a git post-commit hook with "#!/bin/sh\n\n/my/own/script"
-    When I run `lolcommits --enable`
-    Then the output should contain "installed lolcommit hook to:"
-      And the lolcommits git post-commit hook should be properly installed
-      And the git post-commit hook should contain "#!/bin/sh"
-      And the git post-commit hook should contain "/my/own/script"
-      And the exit status should be 0
-
-  Scenario: Enable in a git repo that has git post-commit hook with a bad shebang
-    Given I am in a git repo
-    And a git post-commit hook with "#!/bin/ruby"
-    And I run `lolcommits --enable`
-      Then the output should contain "doesn't start with a good shebang"
-      And the git post-commit hook should not contain "lolcommits --capture"
-      And the exit status should be 1
-
-  Scenario: Enable in a git repo passing capture arguments
-    Given I am in a git repo
-    When I run `lolcommits --enable -w 5 --fork --stealth --device 'My Devce'`
-    Then the git post-commit hook should contain "lolcommits --capture --delay 5 --fork --stealth --device 'My Devce'"
-    And the exit status should be 0
-
-  Scenario: Disable in a enabled git repo
-    Given I am in a git repo with lolcommits enabled
-    When I run `lolcommits --disable`
-    Then the output should contain "uninstalled"
-    And a file named ".git/hooks/post-commit" should exist
-    And the exit status should be 0
-
-  # flakey test sometimes fails
-  # Scenario: Capture doesnt break in forked mode
-  #   Given I am in a git repo named "forked"
-  #   And I do a git commit
-  #   When I run `lolcommits --capture --fork`
-  #   Then there should be exactly 1 pid in "~/.lolcommits/forked"
-  #   When I wait for the child process to exit in "forked"
-  #   Then a directory named "~/.lolcommits/forked" should exist
-  #     And a file named "~/.lolcommits/forked/raw_capture.jpg" should not exist
-  #     And there should be exactly 1 jpg in "~/.lolcommits/forked"
-
-  Scenario: Commiting in an enabled git repo triggers successful capture
-    Given I am in a git repo named "myrepo" with lolcommits enabled
-    When I do a git commit
-    Then the output should contain "*** Preserving this moment in history."
-      And a directory named "~/.lolcommits/myrepo" should exist
-      And a file named "~/.lolcommits/myrepo/raw_capture.jpg" should not exist
-      And there should be exactly 1 jpg in "~/.lolcommits/myrepo"
-
-  Scenario: Commiting in enabled git repo subdirectory triggers successful capture
-    Given I am in a git repo named "testcapture" with lolcommits enabled
-      And a directory named "subdir"
-      And an empty file named "subdir/FOOBAR"
-    When I cd to "subdir/"
-      And I do a git commit
-    Then the output should contain "*** Preserving this moment in history."
-      And a directory named "~/.lolcommits/testcapture" should exist
-      And a directory named "~/.lolcommits/subdir" should not exist
-      And there should be exactly 1 jpg in "~/.lolcommits/testcapture"
-
-  Scenario: Stealth mode does not alert the user
-    Given I am in a git repo named "teststealth"
-    And I do a git commit
-    When I run `lolcommits --stealth --capture`
-    Then the output should not contain "*** Preserving this moment in history."
-    And there should be exactly 1 jpg in "~/.lolcommits/teststealth"
-
-  Scenario: Commiting in stealth mode captures without alerting the committer
-    Given I am in a git repo with lolcommits enabled
-    And I have environment variable LOLCOMMITS_STEALTH set to 1
-    When I do a git commit
-    Then the output should not contain "*** Preserving this moment in history."
-    And there should be exactly 1 jpg in its loldir
-
-  Scenario: Show plugins
-    When I run `lolcommits --plugins`
-    Then the output should contain a list of plugins
-
-  Scenario: Configuring loltext plugin in test mode affects test loldir not repo loldir
-    Given I am in a git repo named "testmode-config-test"
-    When I run `lolcommits --config --test -p loltext` interactively
-      Then I type "false"
-      Then the output should contain "Disabling plugin: loltext - answer with 'true' to enable & configure"
-    And a file named "~/.lolcommits/test/config.yml" should exist
-    When I run `lolcommits --test --show-config`
-    Then the output should match /loltext:\s+:enabled: false/
-
-  Scenario: test capture should work regardless of whether in a vcs repo
-    Given I am in a directory named "not_a_vcs_repo"
-    When I run `lolcommits --test --capture`
-    Then the output should contain "*** Capturing in test mode."
-      And the output should not contain "path does not exist (ArgumentError)"
-      And the exit status should be 0
-
-  Scenario: test capture should store in its own test directory
-    Given I am in a git repo named "randomgitrepo" with lolcommits enabled
-    When I run `lolcommits --test --capture`
-    Then a directory named "~/.lolcommits/test" should exist
-    And a directory named "~/.lolcommits/randomgitrepo" should not exist
-
-  Scenario: last command should work properly when in a git lolrepo
-    Given I am in a git repo
-    And its loldir has 2 lolimages
-    When I run `lolcommits --last`
-    Then the exit status should be 0
-
-  Scenario: last command should work properly when in a git lolrepo subdirectory
-    Given I am in a git repo
-      And its loldir has 2 lolimages
-      And a directory named "randomdir"
-      And I cd to "randomdir"
-    When I run `lolcommits --last`
-    Then the output should not contain:
-      """
-      You don't appear to be in a directory of a supported vcs project.
-      """
-    And the exit status should be 0
-
-  Scenario: Trying to enable while not in a git repo fails
-    Given I am not in a git repo
-    When I run `lolcommits --enable`
-    Then the output should contain:
-      """
-      You don't appear to be in the base directory of a supported vcs project.
-      """
-    And the exit status should be 1
-
-  Scenario: last command should fail gracefully if not in a repo
-    Given I am not in a git repo
-    When I run `lolcommits --last`
-    Then the output should contain:
-      """
-      You don't appear to be in a directory of a supported vcs project.
-      """
-    And the exit status should be 1
-
-  Scenario: Configuring loltext plugin if not in a repo
-    Given I am not in a git repo
-    When I run `lolcommits --config`
-    Then the output should contain:
-      """
-      You don't appear to be in a directory of a supported vcs project.
-      """
-    And the exit status should be 1
-
-  Scenario: browse command should fail gracefully when not in a repo
-    Given I am not in a git repo
-    When I run `lolcommits --browse`
-    Then the output should contain:
-      """
-      You don't appear to be in a directory of a supported vcs project.
-      """
-    And the exit status should be 1
-
-  Scenario: last command should fail gracefully if zero lolimages in lolrepo
-    Given I am in a git repo
-    And its loldir has 0 lolimages
-    When I run `lolcommits --last`
-    Then the output should contain:
-      """
-      No lolcommits have been captured for this repository yet.
-      """
-    Then the exit status should be 1
-
-  Scenario: browse command should work properly when in a git lolrepo
-    Given I am in a git repo
-    And its loldir has 2 lolimages
-    When I run `lolcommits --browse`
-    Then the exit status should be 0
-
-  Scenario: browse command should work properly when in a git lolrepo subdirectory
-    Given I am in a git repo
-      And its loldir has 2 lolimages
-      And a directory named "subdir"
-      And I cd to "subdir"
-    When I run `lolcommits --browse`
-    Then the output should not contain:
-      """
-      You don't appear to be in a directory of a supported vcs project.
-      """
-    And the exit status should be 0
-
-  Scenario: handle git commit messages with quotation marks
-    Given I am in a git repo with lolcommits enabled
-    When I run `git commit --allow-empty -m 'no "air quotes" bae'`
-    Then the exit status should be 0
-    And there should be exactly 1 jpg in its loldir
-
-  Scenario: generate gif should store in the timelapses directory
-    Given I am in a git repo named "giffy" with lolcommits enabled
-      And a loldir named "giffy" with 2 lolimages
-    When I run `lolcommits --timelapse`
-    Then the output should contain "Generating animated timelapse gif."
-      And a directory named "~/.lolcommits/giffy/timelapses" should exist
-      And there should be exactly 1 gif in "~/.lolcommits/giffy/timelapses"
-
-  Scenario: generate gif with argument 'today'
-    Given I am in a git repo named "sunday" with lolcommits enabled
-      And a loldir named "sunday" with 2 lolimages
-    When I run `lolcommits --timelapse --period today`
-    Then there should be exactly 1 gif in "~/.lolcommits/sunday/timelapses"
-
-  @requires_ffmpeg @slow_process
-  Scenario: should generate a lolcommit animated gif
-    Given I am in a git repo named "gif"
-      And I do a git commit
-    When I run `lolcommits --capture --animate=1`
-    Then the output should contain "*** Preserving this moment in history."
-      And a directory named "~/.lolcommits/gif" should exist
-      And a file named "~/.lolcommits/animate/raw_capture.mp4" should not exist
-      And there should be exactly 1 gif in "~/.lolcommits/gif"
-
-  @requires_ffmpeg @slow_process
-  Scenario: should generate a lolcommit video
-    Given I am in a git repo named "video"
-      And I do a git commit
-    When I run `lolcommits --capture --video=1`
-    Then the output should contain "*** Preserving this moment in history."
-      And a directory named "~/.lolcommits/video" should exist
-      And a file named "~/.lolcommits/animate/raw_capture.mp4" should not exist
-      And there should be exactly 1 mp4 in "~/.lolcommits/video"
-
-  @requires_ffmpeg @slow_process
-  Scenario: should generate a lolcommit video and animated gif
-    Given I am in a git repo named "video-and-gif"
-      And I do a git commit
-    When I run `lolcommits --capture -v1 -a1`
-    Then the output should contain "*** Preserving this moment in history."
-      And a directory named "~/.lolcommits/video-and-gif" should exist
-      And a file named "~/.lolcommits/animate/raw_capture.mp4" should not exist
-      And there should be exactly 1 mp4 in "~/.lolcommits/video-and-gif"
-      And there should be exactly 1 gif in "~/.lolcommits/video-and-gif"
-
-  @fake-no-ffmpeg
-  Scenario: gracefully fail when ffmpeg not installed and --animate is used
-    Given I am using a "darwin" platform
-    When I run `lolcommits -c --animate 3`
-    Then the output should contain:
-      """
-      ffmpeg does not appear to be properly installed
-      """
-    And the exit status should be 1
-
-  Scenario: Enable on windows platform setting PATH in git post-commit hook
-    Given I am using a "win32" platform
-      And I am in a git repo
-    When I run `lolcommits --enable`
-    Then the git post-commit hook should contain "set path"
-    And the exit status should be 0
-
-  Scenario: Enable in a naked mercurial repo
-    Given I am in a mercurial repo
-    When I run `lolcommits --enable`
-    Then the output should contain "installed lolcommit hook to:"
-    And the lolcommits mercurial post-commit hook should be properly installed
-    And the exit status should be 0
-
-  Scenario: Enable in a mercurial repo that already has a mercurial post-commit hook
-    Given I am in a mercurial repo
-    And a mercurial post-commit hook with "[hooks]\npost-commit.mine = /my/own/script"
-    When I run `lolcommits --enable`
-    Then the output should contain "installed lolcommit hook to:"
-    And the lolcommits mercurial post-commit hook should be properly installed
-    And the mercurial post-commit hook should contain "post-commit.mine = /my/own/script"
-    And the exit status should be 0
-
-  Scenario: Enable in a mercurial repo passing capture arguments
-    Given I am in a mercurial repo
-    When I run `lolcommits --enable -w 5 --fork`
-    Then the mercurial post-commit hook should contain "lolcommits --capture --delay 5 --fork"
-    And the exit status should be 0
-
-  Scenario: Disable in a enabled mercurial repo
-    Given I am in a mercurial repo with lolcommits enabled
-    When I run `lolcommits --disable`
-    Then the output should contain "uninstalled"
-    And a file named ".hg/hgrc" should exist
-    And the exit status should be 0
-
-  Scenario: Commiting in an enabled mercurial repo triggers successful capture
-    Given I am in a mercurial repo named "myrepo" with lolcommits enabled
-    When I do a mercurial commit
-    Then the output should contain "*** Preserving this moment in history."
-    And a directory named "~/.lolcommits/myrepo" should exist
-    And a file named "~/.lolcommits/myrepo/raw_capture.jpg" should not exist
-    And there should be exactly 1 jpg in "~/.lolcommits/myrepo"
-
-  Scenario: Commiting in enabled mercurial repo subdirectory triggers successful capture
-    Given I am in a mercurial repo named "testcapture" with lolcommits enabled
-    And a directory named "subdir"
-    And an empty file named "subdir/FOOBAR"
-    When I cd to "subdir/"
-    And I do a mercurial commit
-    Then the output should contain "*** Preserving this moment in history."
-    And a directory named "~/.lolcommits/testcapture" should exist
-    And a directory named "~/.lolcommits/subdir" should not exist
-    And there should be exactly 1 jpg in "~/.lolcommits/testcapture"
-
-  Scenario: last command should work properly when in a mercurial lolrepo
-    Given I am in a mercurial repo
-    And its loldir has 2 lolimages
-    When I run `lolcommits --last`
-    Then the exit status should be 0
-
-  Scenario: last command should work properly when in a mercurial lolrepo subdirectory
-    Given I am in a mercurial repo
-    And its loldir has 2 lolimages
-    And a directory named "randomdir"
-    And I cd to "randomdir"
-    When I run `lolcommits --last`
-    Then the output should not contain:
-      """
-      You don't appear to be in a directory of a supported vcs project.
-      """
-    And the exit status should be 0
-
-  Scenario: browse command should work properly when in a mercurial lolrepo
-    Given I am in a mercurial repo
-    And its loldir has 2 lolimages
-    When I run `lolcommits --browse`
-    Then the exit status should be 0
-
-  Scenario: browse command should work properly when in a mercurial lolrepo subdirectory
-    Given I am in a mercurial repo
-    And its loldir has 2 lolimages
-    And a directory named "subdir"
-    And I cd to "subdir"
-    When I run `lolcommits --browse`
-    Then the output should not contain:
-      """
-      You don't appear to be in a directory of a supported vcs project.
-      """
-    And the exit status should be 0
-
-  Scenario: handle mercurial commit messages with quotation marks
-    Given I am in a mercurial repo with lolcommits enabled
-    When I run `touch meh`
-    And I run `hg add meh`
-    And I run `hg commit -m 'no "air quotes" bae'`
-    Then the exit status should be 0
-    And there should be exactly 1 jpg in its loldir