Github issues going stale

Hello guys!

I’ve raised two reproducible issues on GitHub 2 months ago. Both went stale for the second time now, without anyone at least acknowledging them. Can someone please ping somebody from the team to look into it?

The issues are:
https://github.com/nextcloud/desktop/issues/4304
https://github.com/nextcloud/desktop/issues/4306

Thanks,
Stefan

2 Likes

You can reply to the issues if you want to keep them open. Just reply “open please” to the email notification, or on github. Nothing else we can do, because the team makes no guarantees on addressing our issues. :heart:

2 Likes

I replied to the issues both times I got the notification. The first time it worked, and the bot removed the stable label. This time it didn’t care and closed both issues anyway 30 minutes ago. “open please” does not work.
Both issues should receive the teams’ attention since #4304 makes your PC unresponsive and #4306 prevents issues from being reported on GitHub.

1 Like

So this issue still persists. The GitHub bot is being relatively useless, since it closes issues even if you reply.
Should I write my own bot that just comments the date daily into my issues, or just not report issues at all? To make it clear: I’m not asking anyone to work on them right away. Just some acknowledgement so these valid issues are not lost. And the bot stops closing them.

I’m not sure if the forum is the correct place to discuss matters of GH.

But I got your point. And I agree

A solid idea, but only when the stale bot is triggered, which I believe is once a month.

The primary github repo devs literally ask people to to bring discussions here… so, :person_shrugging:

One of the biggest changes that will help us is Discourse adding full support for GIthub issue integration. It is in development right now.

sorry. My bad. Wasn’t aware of that… :frowning:
So it’s all good then

In theory, yes. But that bot is just wild. See Debug Archive filesize / GitHub file upload limitation · Issue #4306 · nextcloud/desktop · GitHub which was closed even though I replied. :person_shrugging:

So I actually got 2 issues here.

  1. A bot doing wild things and no way to contact anyone responsible.
  2. Valid issues “vanishing” due to a wild bot. And apparently nobody from the internal team is at least skimming through issues on a regular basis to assign or sort them. Seems to me like a process that should see some improvement on the Devs side.

Out of curiosity, I just checked on GitHub again: 595 closed tickets with the stale label. And many of them seems similar to what I’ve described.

The bot closed the issue before you’d responded. It also lacks any way to re-open issues, which is why the dev keeps re-opening it…