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

reply to a comment doesn't nest like it does in the web interface #582

Closed
PatrickvL opened this issue Apr 13, 2017 · 9 comments
Closed

reply to a comment doesn't nest like it does in the web interface #582

PatrickvL opened this issue Apr 13, 2017 · 9 comments
Assignees

Comments

@PatrickvL
Copy link

PatrickvL commented Apr 13, 2017

No description provided.

@Tunous
Copy link
Collaborator

Tunous commented Apr 13, 2017

Got an example?

@PatrickvL
Copy link
Author

PatrickvL commented Apr 14, 2017

Each and every time I've used the Reply button from within OctoDroid here, but instead it became separate comments​ : Cxbx-Reloaded/Cxbx-Reloaded#367

Edit: to be clear : I've used the Reply button from within the files tab, on a file, on review comments of others. As you can see in the screenshot posted there, my replies incorrectly ended up as new conversations.

@maniac103
Copy link
Collaborator

https://developer.github.com/v3/repos/comments/#create-a-commit-comment

I don't see any way to specify a reference to another commit there?

@maniac103
Copy link
Collaborator

Hmm, looks like it's possible with PR comments: https://developer.github.com/v3/pulls/comments/#create-a-comment (see 'alternative input' section)

@maniac103
Copy link
Collaborator

This should be reasonably easy to do. I'll look into it.

@maniac103 maniac103 self-assigned this Apr 14, 2017
@PatrickvL
Copy link
Author

Now that was quick! Thanks! Any idea how soon this lands in Google play so people can update OctoDroid the usual way?

@maniac103
Copy link
Collaborator

Ultimately it depends on @slapperwan, but I guess a soon-ish release totally makes sense for the web flow based oauth alone. I wanted to land the comment bottom sheet PR first, but it's probably better not to delay all the other new features for it.

@Tunous @slapperwan Thoughts on this?

@Tunous
Copy link
Collaborator

Tunous commented Apr 14, 2017

Yes, I think that earlier release is a good idea. Comment bottom sheet still needs some more bug fixes and I feel like a few more will pop up. This feature deserves its own release anyway ;) It could also come with some sort of drafts system that I'm thinking about implementing. I'll talk about this more in a new issue once I finish my base idea.

Just should merge #580 before releasing, and I also think that the mark all as read button from notifications screen should disappear once everything is marked read.

@slapperwan
Copy link
Owner

slapperwan commented Apr 15, 2017

I'm currently testing from Master. Web flow oauth must go ASAP. Any other PR that need to be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants