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

[Source] Use a dedicated specs dir if available #13

Merged
merged 2 commits into from
Apr 8, 2013

Conversation

fabiopelosin
Copy link
Member

This setup implies that while the compatibility layer is set in place no, Pod can be named Specs.

@coveralls
Copy link

Coverage decreased (-1.41%) when pulling 616e79b on source_specs_dir into 9084f2a on master.

View Details

@coveralls
Copy link

Coverage remained the same when pulling 1cee2ba on source_specs_dir into 9084f2a on master.

View Details

fabiopelosin added a commit that referenced this pull request Apr 8, 2013
[Source] Use a dedicated specs dir if available
@fabiopelosin fabiopelosin merged commit e79d383 into master Apr 8, 2013
@fabiopelosin fabiopelosin deleted the source_specs_dir branch April 8, 2013 10:04
Ashton-W pushed a commit to Ashton-W/Core that referenced this pull request Nov 2, 2015
[Source] Use a dedicated specs dir if available
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