{"action":"opened","issue":{"url":"https://api.github.com/repos/CeilingTilesUK/markdown-portfolio/issues/5","repository_url":"https://api.github.com/repos/CeilingTilesUK/markdown-portfolio","labels_url":"https://api.github.com/repos/CeilingTilesUK/markdown-portfolio/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/CeilingTilesUK/markdown-portfolio/issues/5/comments","events_url":"https://api.github.com/repos/CeilingTilesUK/markdown-portfolio/issues/5/events","html_url":"https://github.com/CeilingTilesUK/markdown-portfolio/issues/5","id":345811583,"node_id":"MDU6SXNzdWUzNDU4MTE1ODM=","number":5,"title":"More to learn","user":{"login":"github-learning-lab[bot]","id":37936606,"node_id":"MDM6Qm90Mzc5MzY2MDY=","avatar_url":"https://avatars0.githubusercontent.com/in/10572?v=4","gravatar_id":"","url":"https://api.github.com/users/github-learning-lab%5Bbot%5D","html_url":"https://github.com/apps/github-learning-lab","followers_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/followers","following_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/following{/other_user}","gists_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/gists{/gist_id}","starred_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/subscriptions","organizations_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/orgs","repos_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/repos","events_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/events{/privacy}","received_events_url":"https://api.github.com/users/github-learning-lab%5Bbot%5D/received_events","type":"Bot","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-30T15:34:09Z","updated_at":"2018-07-30T15:34:09Z","closed_at":null,"author_association":"NONE","body":"## Nice work\n\nCongratulations @CeilingTilesUK, you've completed this course!\n\n![congratulations](https://octodex.github.com/images/welcometocat.png)\n\n## What went well\n\nDuring this course you successfully:\n\n- Added a checklist to an issue comment\n- Enabled GitHub Pages on your repository\n- Committed changes to your webpage by:\n    - Adding headers to the `01-name.md` file\n    - Including an image in the `02-image.md` file\n    - Creating links to other websites in the `03-links.md` file\n    - Adding your accomplishments to the `04-lists.md` file\n    - Using emphasis like **bold** and _italics_ in the `05-emphasis.md` file\n- Learned about Jekyll Themes\n\n## What's next?\n\nNow that you have mastered the basics of Markdown @CeilingTilesUK, here's some quick information about some of the other cool features we didn't cover.\n\n### More Links in Markdown\n\n<details>\n<summary>Username and Team @mentions</summary>\n\n  ### Username and Team @mentions\n\n  Typing an `@` symbol, followed by a GitHub username, will send a notification to that person about the comment. This is called an “@mention”, because you’re mentioning the individual. You can also `@mention` teams within an organization. For more information, see “[Receiving notifications about activity on GitHub](https://help.github.com/categories/receiving-notifications-about-activity-on-github/) in the *GitHub Help*.\n\n  ```\n  @githubteacher\n  ```\n\n  @githubteacher\n\n  <hr>\n</details>\n\n<details>\n  <summary>Cross Links</summary>\n\n  ### Cross Links\n\n  To bring up a list of suggested issues and pull requests within a repository, type `#`. Type the issue or pull request number or title to filter the list, and then press either Tab or Enter to complete the highlighted result.\n\n  Additionally, references to issues and pull requests are automatically converted to shortened links to the issue or pull request. For example,\n\n  | Reference type | Raw reference | Short link |\n  | -------------- | ------------- | ---------- |\n  | Issue or pull request URL | `https://github.com/desktop/desktop/pull/3602` | [#3602](https://github.com/desktop/desktop/pull/3602) |\n  | `#` and issue or pull request number | #3602 | [#3602](https://github.com/desktop/desktop/pull/3602) |\n  | `GH-` and issue or pull request number | GH-3602 | [GH-3602](https://github.com/desktop/desktop/pull/3602) |\n  | `Username/Repository#` and issue or pull request number | desktop/desktop#3602 | [desktop/desktop#3602](https://github.com/desktop/desktop/pull/3602) |\n\n  For more information, see “[Autolinked references and URLs](https://help.github.com/articles/autolinked-references-and-urls/)” in the *GitHub Help*.\n\n  <hr>\n</details>\n\n<details>\n  <summary>Linking Specific Commits</summary>\n\n  ### Linking Specific Commits\n\n  References to a commit's ID (commonly called a SHA or hash) are automatically converted into shortened links to the commit on GitHub. For example,\n\n  | Reference type | Raw reference | Short link |\n  | -------------- | ------------- | ---------- |\n  | Commit URL | https://github.com/desktop/desktop/commit/8304e9c271a5e5ab4fda797304cd7bcca7158c87 | [8304e9c](https://github.com/desktop/desktop/commit/8304e9c271a5e5ab4fda797304cd7bcca7158c87) |\n  | SHA | 8304e9c271a5e5ab4fda797304cd7bcca7158c87 | [8304e9c](https://github.com/desktop/desktop/commit/8304e9c271a5e5ab4fda797304cd7bcca7158c87) |\n  | User@SHA | desktop@8304e9c271a5e5ab4fda797304cd7bcca7158c87 | [desktop@8304e9c](https://github.com/desktop/desktop/commit/8304e9c271a5e5ab4fda797304cd7bcca7158c87) |\n  | Username/Repository@SHA | User/Repository@SHA: desktop/desktop@8304e9c271a5e5ab4fda797304cd7bcca7158c87 | [desktop/desktop@8304e9c](https://github.com/desktop/desktop/commit/8304e9c271a5e5ab4fda797304cd7bcca7158c87)|\n\n\n  <hr>\n</details>\n\n### Formatting Markdown\n\n<details>\n  <summary>Quotes</summary>\n\n  ### Quotes\n\n  You can create quote text with a `>`.\n\n  ```\n  In the words of Abraham Lincoln:\n\n  > Pardon my French\n  ```\n\n  In the words of Abraham Lincoln:\n\n  > Pardon my French\n\n  <hr>\n</details>\n\n<details>\n  <summary>Tables</summary>\n\n   ### Tables\n\n   You can create tables by assembling a list of words and dividing them with hyphens `-` (for the first row), and then separating each column with a pipe `|`:\n\n    ```\n    First Header | Second Header\n    ------------ | -------------\n    Content from cell 1 | Content from cell 2\n    Content in the first column | Content in the second column\n    ```\n\n  First Header | Second Header\n  ------------ | -------------\n  Content from cell 1 | Content from cell 2\n  Content in the first column | Content in the second column\n\n  For more detail on formatting with tables, see \"Organizing information with tables\" in the _GitHub Help_.\n\n<hr>\n</details>\n\n<details>\n  <summary>Inline Code Blocks</summary>\n\n  ### Inline Code Blocks\n\n  Certain words and phrases need to be formatted in monospace fonts, especially when writing about code. As you've seen throughout this lab, words can be distinguished in markdown with `inline code blocks`.\n\n  Inline code is just one ``` character on either side of the text, and can be used within paragraphs, headers, or other Markdown.\n\n  ```\n  `inline code is just one backtick`\n  ```\n\n  `inline code is just one backtick`\n\n  <hr>\n</details>\n\n<details>\n  <summary>Separate Code Blocks</summary>\n\n  ### Separate Code Blocks\n\n  To separate out a larger block of code, use three ``` characters instead of one, and set the text aside in its own paragraph.\n\n  ```\n  Anything written in this **paragraph** will not be _formatted_ even if it would normally be recognized in this setting. :taco:\n  ```\n\n  Anything written in this **paragraph** will not be _formatted_ even if it would normally be recognized in this setting. :taco:\n  <hr>\n</details>\n\n<details>\n  <summary>Syntax Highlighting</summary>\n\n  ### Syntax Highlighting\n\n  In addition to code blocks, some code blocks should be rendered differently depending on the language, such as Javascript or command-line text.\n\n  What we type:\n\n      ```sh\n      github-learning-lab ~/Projects/recipe-repository\n      $ git init\n      Initialized empty Git repository in /Users/github-learning-lab/Projects/recipe-repository/.git/\n      ```\n\n  What we see:\n  ```sh\n  github-learning-lab ~/Projects/recipe-repository\n  $ git init\n  Initialized empty Git repository in /Users/github-learning-lab/Projects/recipe-repository/.git/\n  ```\n  <hr>\n</details>\n\n<details>\n  <summary>Summary dropdown</summary>\n\n  ### Summary dropdown\n\n  Most of the text in this issue is formatted in collapsible summary blocks. Here's how to make them with Markdown:\n\n  ```\n  <details>\n    <summary>Title</summary>\n\n    Content here\n\n  </details>\n  ```\n\n  <hr>\n</details>\n\nWant to keep learning? Feel free to [check out our other courses](https://lab.github.com/courses).\n\n<hr>\n<h3 align=\"center\">I won't respond to this issue, just close it when you are done!</h3>\n"}}
{"actor":{"display_login":"github-learning-lab"}}