Publishing a monthly report and discussing it so it has consensus from all Forgejo community members was a lot of work the last time. Between two to three full days. It was absolutely worth the result but it is more than I can fit in my schedule.
Yet, these reports are a promise Forgejo made to Codeberg and they must be written, one way or another.
I'll create an issue for that.
I'm going to pick up #150 today and see whether I need to massage it to hold our promise towards Codeberg.
The most time consuming part is going to get a consensus on the content, as it was last month. And make sure nothing was forgotten. I most certainly overlooked things people did that I did not remember.
Closing this issue as we are now in July 2023...
A Feb 2023 report was not published on the Forgejo blog but there have been monthly updates since then. For reference, @dachary puclished a Feb update for Forgejo on his personal blog at https://blog.dachary.org/2023/03/06/my-forgejo-monthly-update-february-2023/.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?