Clarify the introduction of each module so that the student knows when other modules should be run first.
This should fix #76.
Types of changes
What types of changes does your code introduce to Online DevOps Dojo?
Put an x in the boxes that apply
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, renaming)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Workflow change
[x] Documentation update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[ ] I have added necessary documentation (if appropriate).
[ ] Any dependent changes have been merged and published in downstream modules
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Proposed changes
Clarify the introduction of each module so that the student knows when other modules should be run first. This should fix #76.
Types of changes
What types of changes does your code introduce to Online DevOps Dojo? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...