Skip to content

Conversation

thatnerdjosh
Copy link

This provides the ability to setup the common directories needed for
working with rspec-puppet by extracting out the logic that shouldn't be
happening in a control repo which is symlinking (see
#607)

This provides the ability to setup the common directories needed for
working with rspec-puppet by extracting out the logic that shouldn't be
happening in a control repo which is symlinking (see
rodjek#607)
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 85.423% when pulling a3b998a on NerdsvilleCEO:feature/js-allow_users_to_setup_control_repo into 6b29693 on rodjek:master.

@thatnerdjosh
Copy link
Author

Working on tests to bring coverage back up

@thatnerdjosh
Copy link
Author

@rodjek I am having trouble finding the tests for the rspec-puppet-init utility, could you point me to where I should be looking for that?

@DavidS DavidS added the feature label Nov 9, 2020
@DavidS DavidS self-assigned this Nov 9, 2020
Copy link
Collaborator

@DavidS DavidS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @thatnerdjosh ,

thanks for your contribution. I'm less concerned about the coverage, and more about adding a short sentence to https://github.com/rodjek/rspec-puppet/blob/master/docs/documentation/setup/index.md that this also works for control-repos now (and what that means).

@thatnerdjosh
Copy link
Author

Hello @DavidS,

This was so long ago, somehow it slipped my plate... I forgot what a control repo was or what this code was achieving. I'll take a look and then update the docs accordingly.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants