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 ;)
(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 😬)
Nice. #gitea did it; they're now makeing #giteaenterprise where they added already more features. And there's no doubt that they'll continue this path forward, putting more and more effort in the enterprise version and keeping the free version from getting these features via contributions since it would ruin their company.
And best thing is: they already are stealing code. They took stale PR's and put it into the Enterprise version. Thats just disgusting. And unlike gitlab, which EE is not only opensource (i.e. readable), they also have a lot of paid engineers to built their product, unlike gitea, where like 95% of work is done by volunteers, not only now but in the past included. It's espc disgusting for how cheap the features are, like an IP allowlist. Which gets even more sad when you think about what would happen if a volunteer would contribute similar features to the free version. Atleast we have not to guess as it is clearly stated in their contributors guidlines: they have added a clause once they became a company, that they can "politly refuse" any PR by simply not responding. That stinks for me after a tactic of keeping face while not allowing any code that would conflict with the enterprise version.
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.
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.
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.
TIL: When you use #codeberg and/or #forgejo, you can pimp your profile page by creating a repository called .profile (the dot is important) with a single file called README.md in it. Once done, the Markdown in said file will be shown as default content on your profile page. This is going to be fun! https://codeberg.org/jwildeboer
The actual upgrade (and respective database migrations) are running now. The #Forgejo part looks smooth so far, we expect to return to service in about 5 minutes.
@fujowebdev It's nice to see representation of something other than #GitHub, but given that #GitLab is maintained by a forprofit, i expect it's only a matter of time before the same shit starts happening (and there /has/ already been one incident). It'd be cool to see like a cameo (or at least an offhand mention) of something like #Forgejo.
The Forgejo community has just published the 7.0.1 bug fix release[1]. I went to my server, did a systemctl stop forgejo, to stop the rootless container[2] I use to run it, issued podman pull codeberg.org/forgejo/forgejo:7-rootless to get the updates, and finally systemctl start forgejo and done. Updated. Thank you @forgejo for being awesome and working so hard on making things better and better!