githubtraining / communicating-using-markdown Goto Github PK

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.

cc @githubtraining/programs

Bugs

• Persistent: Step 2 follow-up comment does not link to your published site.
• Persistent: Step 2 follow-up comment links to current issue instead of the pull request
  • Image
• Step 4 follow-up links to a broken website.
  • Image
• Persistent: Step 4 follow-up comment links to current PR instead of the next PR.
  • Image
• Persistent: Step 5 should reference _includes/02-image.md instead of _layouts/02-image.md
  • Image
• Persistent: Step 7 follow-up comment links to current PR instead of the next PR.
  • Image
• Step 7 follow-up comment links to a broken URL.
  • Image
• Persistent: Step 10 follow-up comment links to current PR instead of next step
  • Image
• Step 10 links to a broken url
  • Image
• Persistent: Congrats comment needs a quick format fix
• Persistent: Sometimes the web sockets required hard refresh. This was inconsistent.

cc: @JasonEtco

Bugs

• Step 2 follow-up comment does not link to your published site.
• Step 2 follow-up comment links to current issue instead of the pull request
  • Image
• 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.
  • Image
• Step 5 should reference _includes/02-image.md instead of _layouts/02-image.md
  • Image
• Step 7 follow-up comment links to current PR instead of the next PR.
  • Image
• Step 10 follow-up comment links to current PR instead of next step
  • Image
• Congrats comment needs a quick format fix
• Is the URL supposed to update with the Pages url, or point back to Lab as it currently does?
• Sometimes the web sockets required hard refresh. This was inconsistent.

cc: @JasonEtco

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?

👋 Seeing an error here in Step 2, after turning on GitHub Pages: imjohnbo/markdown-portfolio#2. However, it does appear the site deploy was successful.

Bug Report

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:

1. Go to Step 3 Add headers
2. Follow the Activity instructions near the bottom to edit your file with headers
3. After clicking on the 'Files changed' tab...
4. 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.

Bug Report

Current behavior

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:

1. Do the course as if you are a newbie.
2. try clicking something else, anything else and watch.
3. 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! 😄

• Make a list of stuff to learn.
• Make a list of stuff to do.
• Take a break.
• Back to work.
• Finish and submit pull request.

Additional context

Look for screenshots tomorrow.... 👀

Bug Report

Current behavior
I did setting Github Pages and it was published well.
but github-learning-bot didn’t reply to process next step.

issue
web page

Reproduction
Steps to reproduce the behavior in the course:

1. Go to settings
2. Enable Github Pages with master branch and site published

Expected behavior
gitlab-learning bot reply and go to step3

Possible solution

Additional context

thank you.

As you can see, the "See your work" link isn't showing anything:

Thanks to @zeke for the report!

Bug Report

Inside of the "More to Learn" issue, the "Organizing information with tables" link (on the bottom of the Tables drop-down) is not showing anything.

Feature Request

Please link GitHub Guides to this training.

Describe your ideal solution
Link https://guides.github.com/features/mastering-markdown/ to this training.

Describe alternatives you have considered
Link https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github to this training.