Skip to content

Conversation

@matthewhively
Copy link

Included changes:

  • update gitignore to exclude more files/folders
  • slim down the gemspec.files built into the gem, remove un-necessary stuff
  • Updated readme to document all the current environment flags that are recognized
  • Cleaned up a lot of noise within the spec tests themselves
    • Fixed fatal: ambiguous argument 'testsha': unknown revision or path not in the working tree.
    • Fixed fatal: pathspec 'vendor/cache' did not match any files by ensuring vendor/cache exists
    • Removed printouts from Bummr::Remover.instance.remove_commit testing
    • Silenced "display_info" when testing ABORTING bummr update
    • Silenced "puts" when testing
      • outdated_gems
      • writing to log/bummr.log
      • updater
  • Added a printout during spec tests separating which test file is currently running
  • Converted shell execution backticks to %x{} instead
  • Converted quoted backticks to ' instead
  • Excluded several sections from coverage testing
    • cli#display_info - this is just informational for the users. Its always printed.
    • cli#check - redundant with spec/check_spec.rb
    • cli#remove_commit - redundant with spec/lib/remover_spec.rb
    • outdated#gemfile - no need to test whether linux "cat Gemfile" works
  • Tweaked coverage report
    • Write the report into /coverage/<branch_name>
    • Exclude all spec files from coverage

Don't need anything related to testing
 circleci
 spec
 Rakefile

Don't need meta build information
 .ruby-version
 gemspec file
 Gemfile
 Gemfile.lock

Don't need gitignore either
using an invalid sha "testsha" results in:
  fatal: ambiguous argument 'testsha': unknown revision or path not in the working tree.
  Use '--' to separate paths from revisions, like this:
  'git <command> [<revision>...] -- [<file>...]'
Now it is the caller's responsibility to print or not the resulting message

This cleans up some pointless output during spec testing
Also puts statements should use regular ' instead of backticks `
Resolves "fatal: pathspec 'vendor/cache' did not match any files"
 - Write the report into `/coverage/<branch_name>`
 - Exclude all spec files from coverage
Include explanations why they are excluded
@matthewhively
Copy link
Author

matthewhively commented Apr 14, 2025

I have 4 more branches for more specific feature adds/tweaks that are built ontop of this branch.

Version number was updated so that it couldn't be forgotten. I'm not sure how you want to increment it.

@matthewhively
Copy link
Author

You can see pending PRs for the other 4 branches here:
mhively bummer fork PR#1
mhively bummer fork PR#2
mhively bummer fork PR#3
mhively bummer fork PR#4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant