Bump credo from 0.8.10 to 1.5.1

[dependabot-preview]

Bumps credo from 0.8.10 to 1.5.1.

Changelog

Sourced from credo's changelog.

1.5.1

• Fix bug in diff command when run on a subdirectory of a Git repository
• Fix bug in new general param :files when excluding files

1.5.0

• Credo now requires Elixir 1.7 or newer

• Refactor check runner (much faster now for common scenarios)

• Add param allow_acronyms to check Credo.Check.Readability.FunctionNames

• Add name of check to message when printing issues with --verbose

• Add support for "dynamic" tagging for checks via .credo.exs

  # Overwrite all tags for `FooCheck`
  {FooCheck, [tags: [:my_tag]]}
  Add tags for FooCheck
  {SomeCredoCheck, [tags: [:initial, :my_tag]]}
  

  Tags can then be used as usual, via the CLI switch --checks-with[out]-tag:

  # Only run checks tagged `:my_tag` during analysis
  $ mix credo --checks-with-tag my_tag
  Exclude all checks tagged :my_tag from analysis
  $ mix credo --checks-without-tag my_tag
  

New switch to enable file watcher

You can now ask Credo to re-run on file changes:

  $ mix credo --watch

New diff command

You can now ask Credo to only report changes in files that were changed since a given Git ref:

  $ mix credo diff HEAD^
  $ mix credo diff master

You can, of course, combine this with the new --watch switch to iteratively fix issues that have come up since the last release:

  $ mix credo diff v1.4.0 --watch

New general check param :files

You can now include/exclude specific files or patterns for specific checks.

The syntax is the same as for the top-level :files key:

Commits

• 081a9fb Bump version to 1.5.1
• cc22ba1 Update CHANGELOG
• b2bfd43 Update docs and logo
• df71511 Update docs
• 179da52 Merge pull request #822 from adrianomitre/block_pipe_doc_minor_fix
• 247fc91 Add better tests for Sources.find_in_dir/3
• 64f425b Fix files excluded check param
• 19f0748 BlockPipe refactor example minor fix
• 59ee836 Update README
• c4f78a6 Update docs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)