Does anyone know of anyone offering managed Forgejo hosting?
(I don’t mean Codeberg. All my stuff is already on Codeberg. I mean where I could have my own VPS running Forgejo just for our own projects but where I wouldn’t have to deal with managing yet another server.)
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
A UI team was created by Forgejo contributors who have been at work for months on the necessary backports of bug fixes. More ambitious discussions started on the strategies to improve the codebase and the User eXperience. Forgejo needs help to triage. If you ever create a new issue, take a moment of your time to also look at a few others.
If you're wondering what #git forge to host your #opensource code project on, the right answer is probably going to be #forgejo. If the right answer was anything else, you probably wouldn't be wondering about it.
En más noticias internacionales, ayer migré todos los repositorios de un cliente (decenas) de #gitlab a #codeberg porque realmente me gusta #forgejo. Es una pieza fina de software.
(Made it a goal to not require third-party libraries or tools for such a small task, but damn I totally get why nobody is using #Python's builtin HTTP client directly 😬)
GitNex 5.5.0 is now OUT with a new comment UI, the ability to update your profile avatar, the option to insert notes to issues/PRs/releases, and many other improvements.
We have also reached 400 stars on #codeberg. Thanks to all for supporting GitNex all the way.
With the upcoming 6.0.0 release, GitNex will have different version numbers, such as 6.0.0, 7.0.0, and so on.
I hope you enjoy the new release and find it even more productive.
#Gitlab still doesn't support issue templates in #yaml, the way #Github and #Forgejo can. Only #Markdown, which is a lot less attractive. But #Github and #Gitlab can do label changes in the Kanban (project) view, which #Forgejo can't.
You know why I like @forgejo so much? I just did a "fly-by" patch on the documentation because I was annoyed with how complicated that one page was written. So I forked the repo, cleaned up that page and submitted a Pull Request. And guess what? No discussions, no back and forth, it just got merged! Now THAT is how you attract new contributors to your Open Source project. Thank you! My first contribution!
The issue template system in #Forgejo is really powerful, BTW. Here's an example of a yaml issue template[1] and the resulting issue[2]. It sets labels, the branch and adds a nice checklist after you submit the issue. So cool. Oh, and you also get nice looking emails when you create an issue :)
(please don't file test issues in my repo behind those links ;)
So #Forgejo 7.0.2 has been released and it fixed a rather obscure bug I found: Replying to issues via e-mail didn't always add the attachments like screenshots. This is now fixed! Yay! And it was just a systemctl stop forgejo; podman pull codeberg.org/forgejo/forgejo:7-rootless; systemctl start forgejo on my #RHEL9 server! https://forgejo.org/releases/
@morenonatural Sorry, the emoji was mainly expressing that we saw the post and are considering the impact on Codeberg / #Forgejo, and how to potentially improve the situation.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Contributors celebrated the release of Forgejo v7.0 and Codeberg was upgraded the next day. A lot of effort went into the automation of the development process. As Forgejo matures, more and more of the work is about day to day management of bug reports, localization, security, etc. 17 interviews were conducted to better understand how it is used and shape its roadmap.
With #Forgejo v7, there is now experimental code search support. It is currently only available to logged-in users and up to a certain repo size for performance reasons.
Results are generated with git-grep on the fly. We are working on integration with an external search index and also making progress there, but it will take some more time until this is ready.
Now is a good time to get involved with #Forgejo, because the roadmap for the next release is being determined.
Get involved, be it as a designer, frontend or backend developer, translator, user researcher or by helpin to triage bugs and determining feature priority.