Steps 4 and 7 might benefit from a prompt to refresh (I'll handle this one, just leaving this for reference) since it initially appears the merge is blocked without a reviewer (reminder: check data and see if steps 4 or 7 sees any significant fall-out).
Step 4 follow-up comment links to current PR instead of the next PR.
We could revise this course, or create a fork of this course with a separate project to account for people that already have profile READMEs, so that the template repository is the project template repository will actually create a README.md that will appear on the user's profile.
In the Welcome issue, we link to http://gist.github.com. @githubtraining/learning-engineering Can/should we link to the enterprise version, or use a variable to automate this?
Current behavior
Step 3 instruction asks us to click on the pencil icon which does not exist as seen in these screenshots:
Reproduction
Steps to reproduce the behavior in the course:
Go to Step 3 Add headers
Follow the Activity instructions near the bottom to edit your file with headers
After clicking on the 'Files changed' tab...
There will be no pencil icon to click.
Expected behavior
I expect that the lesson will match the instructions and I become disorientated and discouraged when not matched.
Possible solution
Re-word the "in the upper right corner..." to say "click either the pencil or ... (hamburger) for the..."
Additional context
When a final change decision is made, I would like to make the change and commit to my repository then create a pull request to yourselves. If not, then go-ahead and make the changes yourself.
The lesson is broken. The instructions are not clear; the bot gets out of sync easily; the flow is micro-managed not user-managed. Look at the issues above and read that two people got stuck on the second task! (no resolution)
Reproduction
Steps to reproduce the behavior in the course:
Do the course as if you are a newbie.
try clicking something else, anything else and watch.
rest up; I am on it.
Expected behavior
A clear and concise lesson describing what to do and what will happen.
Possible solution
The whole repository needs a good looking over for bugs. I am tired now and will begin tomorrow.
It means I will have to learn bot coding; another learning curve; Ya! 😄