This repository was archived by the owner on May 1, 2022. It is now read-only.
New challenge xml format #172
Open
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
Signed-off-by: northdpole <[email protected]>
Signed-off-by: northdpole <[email protected]>
Signed-off-by: northdpole <[email protected]>
|
We do need more information in case of
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
[Discuss] This is a suggestion for the new challenge.xml format, since both the vagrant and docker container projects are coming along very nicely it's time to discuss how the new challenges are going to look. Whatever we decide I will write the parsing logic and plug it to both projects ;)