(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 #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.
@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.
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 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!
Forgejo v7.0 is available with translations in Bulgarian, Esperanto, Filipino and Slovenian; SourceHut builds integration; support for the SHA-256 hash function in Git; source code search by default and more. It also is the first Long Term Support version. The adoption of semantic versioning is the reason for the version bump from v1.21 to v7.0 and is compatible with existing tools. ✨
Giving up on configuring #forgejo to send e-mails. No matter what I try, it can't authenticate to my mail server. "Password mismatch" though it works without problems when I connect with my normal e-mail client, so I know the password is correct. I tried putting the password as PASSWORD and without the backticks in app.ini, no luck.
SOLVED: The key in app.ini is named PASSWD not PASSWORD. #facepalm
After the #XZ attack, I have a suggestion for all #software forges (#Forgejo, #GitHub, #Gitea, #Sourceforge, etc.):
Have some way to visualize binary files better, including diffs to such files. Cuz now, we have basically nothing except byte counters.
Since they're binary files, it must be as generic as possible. But even some rendering or analysis is better than nothing.
The idea is to expose weird patterns in binary files that could be a sign of an attack.
#Forgejo v1.21.11-1 was just released. It contains a single bug fix for a regression introduced in v1.21.11-0 by which creating a tag via the API would fail with error 500 on a repository where a Forgejo Actions workflow triggered by tags exists. We recommend to upgrade only if you are impacted.
#forgejo doesn't offer something comparable to gists on Github. But that actually allows for a better solution. You cannot create pull requests on gists over on GitHub for "reasons". Which is a bit of a shame.
So I created a repo called "gists" on @Codeberg (which runs on Forgejo) and filled it with, well, gists. So now you can simply read them, clone the repo and create pull requests if you think I said something that needs a bit of correction.