Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

I cannot comment on a specific post in my own repository for some reason: maybe OP blocked me or repo transfer bug #1570

Open
cirosantilli opened this issue May 4, 2019 · 2 comments

Comments

@cirosantilli
Copy link
Collaborator

cirosantilli commented May 4, 2019

This is the thread: cirosantilli/china-dictatorship#42

Someone commented there 5 hours ago so it seems that I'm the only one who can't comment anymore: cirosantilli/china-dictatorship#42 (comment)

The comment box says: "You can't perform this action at this time."

I'm not sure what is the reason for that, but this should never happen since that is my own repository.

Two possible theories I have:

  • I transferred that issue from another repo recently, and archived the original repo, and there is a bug with that. But I also transferred other issues, and I can comment on them.
  • the OP has blocked me after opening the issue. But I seem to be able to create issues on OPs repositories so does not look like it (didn't actually create issues, but "Submit new issue" button does show normally in OPs repo). And even if that is the case, this is a bad implementation, I should always be able to comment on my own repos no matter what.

But maybe it's just some silly setting that I changed and forgot about it ;-)

The conversation is not locked by me.

Ticket ID: 153482

Edit: 1: I had to block OP after reporting this issue because they started to misbehave by editing the title: cirosantilli/china-dictatorship#42 (comment)

We will now find out if blocking an user prevents them from further mutilating their posts.

I recommend the following website behavior:

  • if I block an user, prevent them from making further edits on their posts in my repositories. They may have done useful things in the past, and are now vandalizing their own posts
  • if someone blocks me, it only prevents me from commenting on threads in repositories they own. On my repos, and other people's repos, it should not. Mods of third party repos should mod their own repos.

After blocking the user the "Submit new issue" is greyed out on their repos, which makes sense.

Edit 2 GitHub replied ACKing that this is a bug:

Thanks for reaching out and apologies for the inconvenience. This is the result of a bug on our end. We are currently working to resolve it.

@georgexsh
Copy link

yeah, op has blocked me too and changed the issue title to something hilarious.

@cirosantilli
Copy link
Collaborator Author

Thanks for letting me know, updated issue now.

@TPS TPS added the comments label May 5, 2019
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

3 participants