We too just switched to bare repos and haven't really missed much from the SCM frontends.
We too just switched to bare repos and haven't really missed much from the SCM frontends.
That's the one example I'm referring to.
Since then, we faced a number of UI bugs that we just didn't bother to report since most other attempts at reaching out were rejected as "not our problem".
- https://github.com/go-gitea/gitea/pull/15268
- https://github.com/go-gitea/gitea/pull/14726
- https://github.com/go-gitea/gitea/pull/15315
- https://github.com/go-gitea/gitea/issues/14639
We're a volunteer team, so any information you can add to an issue would be greatly appreciated. Even if you're not using Gitea anymore.
Does this extend also to the case of when someone submits a pull request to them, or only for issues that people file?
If the former then it is truly problematic. If the latter they may be simply overworked/overburdened by the volume of issues that are being filed, and could need more people submitting pull requests instead of opening issues.
Although merging and reviewing a pull request can also be quite time-consuming. If you are already overworked, it might add to the problem. I'm happy that none of my open-source projects went through the roof. I won't be able to manage it alone.
The maintainer has responded more recently than the GP's last comment. "ignore" feels like a stretch.
Please stop assuming malice in others. You'll be a happier person.
I've responded to the dev, FWIW.