| Forgejo | https://forgejo.org |
Earl Warren
- 40 Followers
- 16 Following
- 249 Posts
It would be good to add it to https://codeberg.org/forgejo-contrib/delightful-forgejo 🙏
@wonshu @forgejo This is for the benefit of scripts and other clients in the Gitea ecosystem.
If they were modified to detect Gitea compatibility by parsing the version, they can keep doing that.
In truth I doubt any script actually does that but... there really is no way to know for sure.
As time passes this becomes less and less relevant and it will eventually be removed when the odds of an incompatibility is believed to reach epsilon.
@magostinelli @forgejo yes, only PostgreSQL but the root cause is not PostgreSQL specific. It actually is a bug that has been lurking for years, waiting to strike. And it did 😱
fix: db.Iterate can miss records, can return records twice
Fixes #9644. Rewrites `db.Iterate` so that it performs DB queries in this format: - First: `SELECT ...columns... FROM table ORDER BY id LIMIT ...buffer-size...` - Subsequent buffer fills: adding a `WHERE id > ...last-id-from-previous...` This approach: - Prevents records from being missed or re...
If you do not use Forgejo Actions you are not impacted at all.
Gusted@mxfraud Allowing AI contributions is misleading and not what the agreement is about.
If you think about (problematic) ways that people use AI for you would see that the agreement would not allow it. The allowed use of AI is really limited.
I encourage you to read the discussion that lead to this agreement, this is the best outcome IMO - pushing anything beyond this would not have been possible. There's no BDFL, it had to be agreed by those involved in Forgejo which include people that use AI in some form.
https://codeberg.org/forgejo/discussions/issues/366
I can totally understand that anything that isn't a total AI ban is not good (I myself would've liked to see this too), but achieving that is not realistic if you work with a diverse group of people. This is the best compromise.
On the use of AI in the context of Forgejo
Hey everyone, I'd like to continue the discussion from https://codeberg.org/forgejo/forgejo/pulls/8285 because I think it is an important one to have. There have been bilateral conversations about this matter between me and several other team members, but I suppose that it's time to discuss th...
@Mehrad @forgejo I see https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/Changelog but there is no mention of forgejo.
@ikonoklast @mobergmann it will show on the first commit.
@lukasrotermund @forgejo https://codeberg.org/forgejo-contrib/federation/ is where it is cooking. You will find information on every monthly update too.
