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

Support git fixture branches containing slashes #297

Merged

Conversation

trevor-vaughan
Copy link
Contributor

Previously, checking out git feature branches containing slashes would
consistently fail.

This modifies the command to unambiguously point to origin.

Previously, checking out git feature branches containing slashes would
consistently fail.

This modifies the command to unambiguously point to origin.
@trevor-vaughan trevor-vaughan requested a review from a team as a code owner November 5, 2019 01:14
@codecov-io
Copy link

codecov-io commented Nov 5, 2019

Codecov Report

Merging #297 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #297   +/-   ##
=======================================
  Coverage   43.75%   43.75%           
=======================================
  Files          11       11           
  Lines         825      825           
=======================================
  Hits          361      361           
  Misses        464      464
Impacted Files Coverage Δ
lib/puppetlabs_spec_helper/tasks/fixtures.rb 38% <0%> (ø) ⬆️

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 671244f...805ad89. Read the comment docs.

@puppetcla
Copy link

CLA signed by all contributors.

@DavidS DavidS merged commit 4cca45b into puppetlabs:master Nov 15, 2019
glennsarti added a commit to glennsarti/puppetlabs_spec_helper that referenced this pull request Jan 31, 2020
Previously if you added a ref with a forward slash, which is common in branch
names, this would fail in a strange way.  This commit adds early detection of
forward slashes and returns a helpful error message.
glennsarti added a commit to glennsarti/puppetlabs_spec_helper that referenced this pull request Jan 31, 2020
Previously if you added a ref with a forward slash, which is common in branch
names, this would fail in a strange way.  This commit adds early detection of
forward slashes and returns a helpful error message.
glennsarti added a commit to glennsarti/puppetlabs_spec_helper that referenced this pull request Feb 4, 2020
Previously if you added a ref with a forward slash, which is common in branch
names, this would fail in a strange way.  This commit adds early detection of
forward slashes and returns a helpful error message.
glennsarti added a commit that referenced this pull request Feb 4, 2020
(GH-297) Don't allow git refs with forward slashes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants