Title: More clarity needed around tasks to create & resolve issues · Issue #40 · feiphoon/github-workshop · GitHub
Open Graph Title: More clarity needed around tasks to create & resolve issues · Issue #40 · feiphoon/github-workshop
X Title: More clarity needed around tasks to create & resolve issues · Issue #40 · feiphoon/github-workshop
Description: Describe the bug Some attendees asked what they were meant to do, and I am worried that the concept of issues was a bit too vague. I initially believed a list of casual questions would have been okay for them to pick from, but I think th...
Open Graph Description: Describe the bug Some attendees asked what they were meant to do, and I am worried that the concept of issues was a bit too vague. I initially believed a list of casual questions would have been ok...
X Description: Describe the bug Some attendees asked what they were meant to do, and I am worried that the concept of issues was a bit too vague. I initially believed a list of casual questions would have been ok...
Opengraph URL: https://github.com/feiphoon/github-workshop/issues/40
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"More clarity needed around tasks to create \u0026 resolve issues","articleBody":"**Describe the bug**\r\nSome attendees asked what they were meant to do, and I am worried that the concept of issues was a bit too vague. I initially believed a list of casual questions would have been okay for them to pick from, but I think they may have been stuck on how to imagine the topics as issues, and I can't say for sure how many did not gloss over the instructions (also because their application might have been unclear in the context).\r\n\r\nIn addition, I noticed that some attendees created files without extensions (so either did not know about Markdown files, or it did not occur to mimic them from the README.md), though GitHub handled this like a champ. The second point might not need solving at all for the purposes of the exercise, because I am in two minds about adding to their load at this stage by explaining Markdown files.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n- Well, impossible to reproduce right now unless we put some fresh beginner eyes on this, but it's here: https://github.com/feiphoon/github-workshop/tree/master/workshop/03-creating-issues \r\n\r\n**Expected behavior**\r\nFor them to create an issue each, with appropriate title \u0026 description, and information to resolve the issue, that can be clearly actioned in and connected to the next part of the exercise.\r\n\r\n**Suggestions to solve**\r\nOpen to discussion.\r\n- A screenshot of an issue form showing sample text\r\n- A set of precise content to transfer and input, with instructions on how to solve, but without any solutions.\r\n- To point out Markdown, or to let that slide for now?\r\n","author":{"url":"https://github.com/feiphoon","@type":"Person","name":"feiphoon"},"datePublished":"2019-03-01T23:41:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/40/github-workshop/issues/40"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:d630b461-1884-6825-2386-47d8bb407fd8 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B960:D4C17:1636335:1CE9CA6:69803D10 |
| html-safe-nonce | cb2f6923facf0318c274809127cf7b5e1dc112a792552416396e0427d97c7d28 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCOTYwOkQ0QzE3OjE2MzYzMzU6MUNFOUNBNjo2OTgwM0QxMCIsInZpc2l0b3JfaWQiOiI1NzA0MzQ5Njc5MTAyMjEzMzkyIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 3bd43290154b479f057c26d8268f45ad08f87dae4e08bb93d7f5b7d5439769be |
| hovercard-subject-tag | issue:416322314 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/feiphoon/github-workshop/40/issue_layout |
| twitter:image | https://opengraph.githubassets.com/521858f4f4df263c66faa36af5b565faa902e574e415b01a06ed581bc5a74250/feiphoon/github-workshop/issues/40 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/521858f4f4df263c66faa36af5b565faa902e574e415b01a06ed581bc5a74250/feiphoon/github-workshop/issues/40 |
| og:image:alt | Describe the bug Some attendees asked what they were meant to do, and I am worried that the concept of issues was a bit too vague. I initially believed a list of casual questions would have been ok... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | feiphoon |
| hostname | github.com |
| expected-hostname | github.com |
| None | 60279d4097367e16897439d16d6bbe4180663db828c666eeed2656988ffe59f6 |
| turbo-cache-control | no-preview |
| go-import | github.com/feiphoon/github-workshop git https://github.com/feiphoon/github-workshop.git |
| octolytics-dimension-user_id | 1391178 |
| octolytics-dimension-user_login | feiphoon |
| octolytics-dimension-repository_id | 170326311 |
| octolytics-dimension-repository_nwo | feiphoon/github-workshop |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 170326311 |
| octolytics-dimension-repository_network_root_nwo | feiphoon/github-workshop |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 7c85641c598ad130c74f7bcc27f58575cac69551 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width