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

Added data-contents-only support, based on kelvinhammond's attempt to do the same. #7

Closed
wants to merge 1 commit into from

Conversation

douglas-treadwell
Copy link

This one passes all the unit tests, including new unit tests for the feature.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.34%) when pulling bd6fe07 on douglas-treadwell:master into a1ee1f7 on wmluke:master.

@douglas-treadwell
Copy link
Author

Closing due to some conflicting metadata. Reopened as a separate PR.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.34%) when pulling 2b1b1fb on douglas-treadwell:master into a1ee1f7 on wmluke:master.

@douglas-treadwell
Copy link
Author

You could merge either this or PR 8, but by the time you read this I will probably have re-closed this PR.

I reopened it because I realized that by closing it I froze the history displayed by GitHub, and I have since updated the history on my branch. Given that you hadn't merged yet I thought I would correct my mistake. Anyway, in hindsight I realize that closing the PR and opening a new one was unnecessary -- I could've done the same with the original PR. My apologies for potentially spamming your email with a duplicate PR and some extra comments.

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

2 participants