Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Remove errant </div> from README #1
Merged
Conversation
There was a stray closing div tag in the README that caused a rendering failure on the forge.puppetlabs.com module page. Removing that tag should be meaningless for the REAMDE and correct the bug on Forge.
|
Thanks =) |
MichaelBlume
pushed a commit
that referenced
this pull request
Jan 31, 2014
Remove errant </div> from README
|
Just updated the released on puppet forge On Jan 30, 2014, at 4:26 PM, Michael Blume notifications@github.com wrote:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
There was a stray closing div tag in the README that caused a
rendering failure on the forge.puppetlabs.com module page. Removing
that tag should be meaningless for the REAMDE and correct the bug
on Forge.
Thanks for publishing your module to the Forge! Sorry for the trouble. Once you release a version with this patch, the module page should look as we intend it. For the future, we'll also update the Forge to not bug out when we get an errant tag like this.