Кстати, если кто вдруг не в курсе, то то ли в последний LTS, то ли в один из предыдущих релизов Forgejo завезли возможность push-зеркалирования через SSH-ключи.

И это просто замечательно, учитывая, что зеркализоваться в тот же Github через токены было болью: либо нужно было выписывать вечный легаси токен, который может дофига лишнего, либо выписывать гранулированные токены не реже, чем раз в год и обновлять во всех репозиториях Forgejo/Gitea, что вызывало жопоболь.

Теперь можно просто создать конфигурацию зеркалирования в Forgejo, оно создаст SSH-ключ для этого, который можно будет добавить на гитхабе как Deploy-ключ, у которого никакого доступа, кроме записи (и чтения) в репозиторий не будет.

#Forgejo: Why can't I make a repository public in my limited profile? Why can't I make a repository limited in my public profile?

This week in #FDroid (TWIF) is live:

* #kitshn for #Tandoor update mixup
* #etchdroid 2.0 now w/ #MaterialDesign
* #KOReader for more devices
* fight #quantum with #Tuta #postquantum #email and #calendar
* 20 years of #git, get #forgejo and #gitnex
* #OrganicMaps community open letter
* #ToSDR to the rescue
+ 8 new apps
+ 92 updates
& 4 archived

Git clone this post: https://f-droid.org/2025/04/17/twif.html

Brew (https://brew.bsd.cafe) has been upgraded to Forgejo 11.0.0

Brew (https://brew.bsd.cafe) has been upgraded to Forgejo 11.0.0

#Forgejo 11.0.0 was just released!

We recommend that all installations are upgraded to the latest version.

It comes with a number of new features and improvements making user experience more convenient and productive. It features a new UI language, easy access token regeneration, better search options, and makes it possible to download entire folders in one click. As an LTS version, it will be supported until 15 July 2026.

Read more at https://forgejo.org/2025-04-release-v11-0/

I just migrated my first repository from github to my own forgejo instance on my new dedicated Hetzner server. Wow, that's liberating! A few more repositories will follow today!

Обновил у себя Forgejo с 7.x.x LTS до 10.x.x Stable.

Думал, что придётся попердолиться с поломками обратной совместимости что-то опять поудалять или подобавлять в конфиг.

Сначала натравил на релизноты и чейнджлоги последних трёх мажоров ChatGPT и попросил сделать выжимку.

Почитал, не поверил, пошёл читать сам.

В итоге обновился буквально тем, что у себя в .env файле поменял версию образа с 7 на 10 и дёрнул:

docker compose pull
docker compose up -d

Потом ещё для перестраховки пошёл и проверил с помощью forgejo doctor check --all, что ничего не сломалось.

Там были ровно те же ворнинги, которые были ещё со времён переезда с Gitea на 7.x.x - заодно пофиксил их.

Короче, выражаю свой респект господам из @forgejo за достойный переход на SemVer, достойное ему следование и достойное избегание лишних поломок даже между мажорными версиями

P.S. Надо будет теперь где-нибудь в конце апреля заехать на выходящий скоро свежий LTS релиз и снова долго в ус не дуть обновляя минорные версии автоматом.

Hello #Aachen (and nearby areas)! If you're interested in contributing to alternatives of big proprietary platforms (like #Codeberg :D - that being the alternative), I'm organizing a #Forgejo contribution workshop at the @cccac on Sunday, 27.04.2025 (two weeks), starting from 13:00.

(EDIT: Changed the date because I forgot about Easter.)

Click here for more details.

Just reminded of how cool (and handy) it is that my #Forgejo instance has an inbuilt #Docker container repository. Loving the #libre lifestyle.

I want a "Github Desktop" app but just for like all got stuff. I suck at got and remembering all the little weird commands any time I need to do something outside fetch, push, pull. I know there are a few different git GUIs out there but none of them have the simplicity of Github Desktop. I don't plan on doing anymore personal projects on github and moving to codeberg and a self-hosted Forgejo for private repos. but it stinks to lose my personal favorite workflow.
#Github #Codeberg #Git #Forgejo

Life Without GitHub: What's it like? Let's talk about #Forgejo Git Forge ... And whether Apache #NuttX RTOS could possibly coexist with GitHub and our own Git Forge

Article: https://lupyuen.org/articles/forgejo.html

new release of fj.el, an #emacs #forgejo / #codeberg client. it adds:

- pagination of most views
- generic next/prev page functions
- generic reload engine, making it trivial to reload a specific view while changing a single parameter
- basic milestones support (add to existing issue, add while composing, display when viewing)
- new macro to handle optional parameters (in fedi.el), makes handling the full API much easier
- render item markdown using instance API (removes need for markdown binary)
- use server default for limit arg always
- mark notification read upon viewing item
- toggle notifications view read/unread/all
- cycle notification type
- list issues by milestone/label
- render PR review diffs and discussion in PR view
- display/add/remove reactions
- implement font-locking of issue numbers/user handles while composing
- add labels while composing
- fix multibyte encoding errors
- handle repos that you do not own yourself (via git)
- quote region in reply buffer
- cycle list own items by state and type (accross all repos)
- handle auth-source for encrypted access tokens
- support repos on different Forgejo instances via .dir-locals.el settings.

there's much need for improvement still, but it's coming along well.

GitNex 8.0.3 is out with fixes for a few bugs that affect all users. Update when you can. :)

- Fix offline cache affecting online activities
- Fix glide for self-signed certificates

https://codeberg.org/gitnex/GitNex/releases

Hm... so this new AI thing from @gitea ... it's definitely interesting, and many people aren't reading, again.

So, what did they do?

They basically created an API client that is usable for LLMs - meaning that LLMs can now directly interact with Gitea. It's not integrated into the server by itself, and nobody is required to use it. Basically, it's HTTP MCP. It's like an API client for a programming language. So it's not a bad thing in itself.

Also, this client by itself doesn't crawl other sites / uses data that was crawled from other sites, since it's literally just an API client.

BUT (!) you have to use an existing LLM model using a client (e.g. Cursor) to be able to use this API client. Now that's the interesting part... I don't know if there's actually a good LLM that only learned from data that it was allowed to use. This means, that Gitea kind of promotes using LLMs that crawled people's sites without their permission.

Sadly, the screenshots shown in the blog post by Gitea don't show what model they are using, so we can't tell if they are using a good or a bad model. (Though, I'm not sure if we specifically need to know that in this case.)

Anyway, I'm always happy to see people switch to @forgejo. I, personally, used it almost since I started moving away from GitHub / -Lab and I love it. Sadly, I know a few people who can't yet move to Forgejo since they're using architectures that Forgejo doesn't build for docker yet.

For those people who are still angry and "need to" be aggressive towards the devs: Calm down, maybe read my blog post that I made in collaboration with Finnley about outrage (https://steffo.blog/outrage-warps-reality/) and have a great day. Maybe go for a walk outside?

Anyway, have a lovely day!

The #Forgejo monthly update was published It is a high level overview of the project activities.

Forgejo v11.0 is on track for release on 16 April 2025. New versions of v7.0 and v10.0 have been released. Improvements to the availability of Forgejo actions have been completed and the Forgejo runner has received new versions. The DDoS attack on code.forgejo.org has ceased and precautions have been taken for the future.

https://forgejo.org/2025-03-monthly-update/

GitNex 8.0.1 is out to fix a few bugs including offline mode.

https://codeberg.org/gitnex/GitNex/releases

*Decentralized source code hosting: we can do better.*

- #Github succeeded in providing us a space to swarm.

- #Gitlab #Forgejo and others gave us sovereignty back over our code hosting.

.

- @radicle now brings communication back between those independent hosts.

(Works like the #fediverse )

.

This #git forge is a big step on the path to freeing uncensored project collaboration.

A much needed tool to bulletproof #foss

https://radicle.xyz/