Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PR single comments are not visible on Conversations tab #5105

Closed
2 of 7 tasks
filipnavara opened this issue Oct 18, 2018 · 11 comments · Fixed by #9143
Closed
2 of 7 tasks

PR single comments are not visible on Conversations tab #5105

filipnavara opened this issue Oct 18, 2018 · 11 comments · Fixed by #9143
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@filipnavara
Copy link
Contributor

Description

Adding a comment by starting a review and then submitting it with "Comment" button is visible on the Conversations page (eg. https://try.gitea.io/filipnavara/test/pulls/1).

@jonasfranz
Copy link
Member

This is not a bug, it's expected behaviour. Please try to add "Single Comment" at GitHub. It won't show up at the timeline.

@jonasfranz jonasfranz added the reviewed/wontfix The problem described in this issue/fixed in this pull request is not a problem we will fix label Oct 18, 2018
@filipnavara
Copy link
Contributor Author

@JonasFranzDEV Definitely not true. I tried it now - filipnavara/test#1.

@jonasfranz
Copy link
Member

@filipnavara At the time the feature got developed, this was not true. But I don't know if we want to go with GitHub's solution because it results in having no difference between Comments inside a Review (type Comment) and Code comments.

@jonasfranz
Copy link
Member

@filipnavara Please have a look at the 4. TODO item at #3748

An option for solving this issue might be to automatically create a review if a single comment gets added. But we should discuss if we want this actually since it bloats the timeline.

@jonasfranz jonasfranz added type/proposal The new feature has not been accepted yet but needs to be discussed first. and removed reviewed/wontfix The problem described in this issue/fixed in this pull request is not a problem we will fix labels Oct 18, 2018
@filipnavara
Copy link
Contributor Author

filipnavara commented Oct 18, 2018

It's been working like that in GitHub for at least a year and I use it all the time. Sometimes it's delayed by few seconds due to some infrastructure issues, but it always showed up. The problem is that there's no way whatsoever to tell that someone has commented on the code without actually going to the code and scrolling down.

Note that GitHub also has the notion of commenting on specific commit, which IIRC, didn't show up on the PR.

@jonasfranz
Copy link
Member

@filipnavara E-Mail notifications will be sent. But I see your point and I propose to add this functionality to "Add single comment".

@filipnavara
Copy link
Contributor Author

E-mail notifications are great if they are enabled, which was not the case for us. ;-)

@filipnavara
Copy link
Contributor Author

Apparently even single comment on a specific commit in a PR still shows up on GitHub now (filipnavara/test#2), but I am fairly certain that was not always the case or that I hit some edge cases where it was not included in the conversation.

@andreymal
Copy link

I think it's an important feature. It's very easy to miss a helpful or important comment without it. The GitHub behavior does not matter here.

@lakesare
Copy link

As a side note, - right now Github does always show single comments, but it's true that it can get delayed, e.g. one of my comments got delayed 18 minutes.

@lafriks
Copy link
Member

lafriks commented Nov 20, 2019

I agree that single comment should show just like review comment

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
DanielYang59 referenced this issue in materialsproject/pymatgen Aug 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants