hello-world: set auto-approve to true #1482
Merged
Conversation
This file contains 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
The first core exercise on the track should be auto-approved. This means that mentor approval isn't needed in order to move forward when the exercise has been completed. Currently any hello-world exercises are auto-approved in the backend of v2 but this special handling might be removed later which is why this also needs to be set in config.json.
sjwarner-bp
approved these changes
Jun 12, 2018
|
Thanks for the quick fix @FridaTveit 🎆 |
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.
The first core exercise on the track should be auto-approved. This means that mentor approval isn't needed in order to move forward when the exercise has been completed.
Currently any hello-world exercises are auto-approved in the backend of v2 but this special handling might be removed later which is why this also needs to be set in config.json.
This fixes the last point in issue #1481.
Reviewer Resources:
Track Policies