vvskl / skills-connect-the-dots

My clone repository

Connect the dots in a GitHub repository

Useful tips when navigating through your repository.

Step 1: Resolve duplicate issues

Welcome to the course 🎉

GitHub has special capabilities to help reference other information on GitHub. For example, when you reference another issue or pull request by number, that number will be hyperlinked. At the same time, a cross-reference is created in the linked issue or pull request. This two-way reference helps people track the relationship of information across GitHub.

With collaboraration from multiple team members, sometimes issues can be duplicated. In the above example, the new issue #8346 is a duplicate of a previous issue #8249. The cross-reference ability allows you to track these duplications and close issues when appropriate.

Creating references

When you link to another issue, a reference within GitHub is automatically created. In fact, you don't even need to include the full link. If you were to type #5 within a comment, that would turn into a link to issue or pull request number 5.

When you want to create a crosslink, start typing the title of an issue or pull request directly after you type the # symbol. GitHub will suggest issues or pull requests that will link to the right place. To learn even more, check out the Autolinked References and URLs article.

⌨️ Activity: Find and close the cross-linked issue

1. Navigate to the issue #1 (Welcome)
2. Type "Duplicate of #2" as a comment and close issue #1
3. Wait about 20 seconds then refresh this page (the one you're following instructions from). GitHub Actions will automatically update to the next step.

---

Get help: Post in our discussion board • Review the GitHub status page

© 2023 GitHub • Code of Conduct • MIT License

skills-connect-the-dots's Issues

Fix the sidebar

GIVEN:

• User opens _sidebar.md file

WHEN:

• User navigates by clicking on [Documentation references] link

THEN (EXPECTED):

• [Documentation references] page must be open successfully

OBSERVED:

• File not found error OR GitHub reports HTTP 404 error (file not found)

Welcome

GIVEN:

• User opens _sidebar.md file

WHEN:

• User navigates by clicking on [Documentation references] link

THEN (EXPECTED):

• [Documentation references] page must be open successfully

OBSERVED:

• File not found error OR GitHub reports HTTP 404 error (file not found)