bob: Lock problem description to match current implementation #132
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We need to be able to regenerate the exercise READMEs without causing the README for 'bob' to drift. A new rule has been added to the upstream problem specification, and this hasn't yet been implemented in this track.
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to be able to regenerate the exercise READMEs without
causing the README for 'bob' to drift.
A new rule has been added to the upstream problem specification,
and this hasn't yet been implemented in this track.
I only realized after submitting #131 that I needed to regenerate the exercise READMEs in order to move forward with exercism/meta#94, which would cause 'bob' to get out of sync.
Since this is a purely janitorial change, I am going to go ahead and merge it when the build passes.
I'm adding a note to the ambiguity issue about deleting this file when the test suite gets updated.