Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove duplicate dry from readme #113

Merged
merged 1 commit into from
Apr 2, 2019
Merged

Conversation

mkungla
Copy link
Contributor

@mkungla mkungla commented Mar 13, 2019

No description provided.

@codecov-io
Copy link

codecov-io commented Mar 13, 2019

Codecov Report

Merging #113 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #113   +/-   ##
=======================================
  Coverage   98.64%   98.64%           
=======================================
  Files           1        1           
  Lines          74       74           
  Branches       25       25           
=======================================
  Hits           73       73           
  Misses          1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c0f798a...8fbf1f4. Read the comment docs.

@chrisblossom
Copy link
Collaborator

Thanks for the PR, but this isn't a duplicate dry entry. It is there as an example because it is required when using dangerouslyAllowCleanPatternsOutsideProject.

@mkungla
Copy link
Contributor Author

mkungla commented Mar 14, 2019

@chrisblossom aight. There could be a comment at least then, right now you have there something which can be read as duplicate key.
You have dry at the beginning of that example and dry after dangerouslyAllowCleanPatternsOutsideProject

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.

None yet

3 participants