Timeline for Github etiquette: Is it polite to help for issue triage?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 21, 2020 at 9:02 | history | edited | Akita | CC BY-SA 4.0 |
Typos and puntuation
|
| Dec 12, 2019 at 10:36 | history | edited | Akita | CC BY-SA 4.0 |
Minor typo fix
|
| Nov 28, 2019 at 13:35 | vote | accept | Akita | ||
| Jan 21, 2020 at 8:59 | |||||
| Nov 27, 2019 at 13:05 | answer | added | planetmaker | timeline score: 6 | |
| Nov 26, 2019 at 12:07 | comment | added | Bart van Ingen Schenau | That was why I wrote it as a comment. I knew that I didn't answer your question. | |
| Nov 26, 2019 at 10:32 | answer | added | MadHatter♦ | timeline score: 8 | |
| Nov 26, 2019 at 9:14 | comment | added | Akita | Thanks @BartvanIngenSchenau . If I do it, I'll try to do it good, of course. But my question is more about: should I? | |
| Nov 25, 2019 at 18:04 | comment | added | Bart van Ingen Schenau | If you decide to add comments recommending closing a ticket, be sure to make it as easy as possible to verify your claim why the ticket can be closed. For example by providing a reference to the pull request that contains the fix that resolves the issue and why that resolves the issue. | |
| Nov 25, 2019 at 13:20 | review | First posts | |||
| Nov 25, 2019 at 14:16 | |||||
| Nov 25, 2019 at 13:16 | history | asked | Akita | CC BY-SA 4.0 |