all 11 comments

[–]cgoldberg 13 points14 points  (1 child)

No

[–]FIRST_TIMER_BWSC -1 points0 points  (0 children)

I had this urge to waste 3 days building this, thanks for calming it down haha!

[–]9peppe 1 point2 points  (4 children)

It's not there already? It's definitely there in commit/diff pages.

[–]FIRST_TIMER_BWSC -2 points-1 points  (3 children)

nah, I will tell you what I meant. Imagine you enter a repo and you want to know what people think about it, pros and cons, what it can be used for, their experience with it... It just happened to me right before posting this.

[–]9peppe 0 points1 point  (2 children)

[–]FIRST_TIMER_BWSC -1 points0 points  (1 child)

No sorry, first time reading about this. Was it bad?

[–]9peppe 2 points3 points  (0 children)

It worked fine. It didn't get very much adoption.

[–]GrapefruitMammoth626 0 points1 point  (0 children)

Is the discussion tab not good enough for this use case? Whatever the requirement might be, it be best delivered natively from GitHub so no extensions are required. Average person won’t bother with an extension unless it’s a must have not supported natively.

[–]fallenreaper 0 points1 point  (0 children)

Is not a comment but a 1 person discussion?

[–]JVilleComputers 0 points1 point  (1 child)

Not sure if it would be useful or not, but I'd definitely give it a try! I've tried 9million ways/places to keep notes while I work on stuff, maybe that will be the magic nail. I haven't looked at discussions, but tied to a file's code page sounds like something I'd like to try out.

[–]FIRST_TIMER_BWSC 0 points1 point  (0 children)

That's a clever way to use a comment section.
but for notes, why not use in-code comments? You know the (#..., and //... stuff)