Forgejo

Beyond coding. We forge.

:forgejo: Website: https://forgejo.org
:codeberg: Source code: https://codeberg.org/forgejo/forgejo
:keyoxide: ID proofs (Keyoxide): https://keyoxide.org/contact@forgejo.org
:matrix: Matrix space: https://matrix.to/#/#forgejo:matrix.org

Public Key

npub12r320mcnpx7hnsr9v8ydwdk9eyqrlpm8usvspwzpd4hw8g5l9rdscrzz58

NIP-05 Address

forgejo_at_floss.social@momostr.pink

Profile Code

nprofile1qqs9pc48aufsn0tecpjkrjxhxmzujqplsan7gxgqhpqk6mhr520j3kcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsg0u6lk

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub12r320mcnpx7hnsr9v8ydwdk9eyqrlpm8usvspwzpd4hw8g5l9rdscrzz58

Show more details

Last Notes

2026-03-30 12:43:15 UTC

- reply

Sounds a bit like the open feature request https://codeberg.org/forgejo/forgejo/issues/1410 for the first wish. The second one indeed is a goal for federation.
~ @npub1c7x…yhh5

2026-03-30 12:06:52 UTC

- reply

Thanks for reporting! Translation happens at https://translate.codeberg.org/engage/forgejo/
In the meantime, I proposed a fix for the string you reported: https://translate.codeberg.org/translate/forgejo/forgejo/nl/?checksum=6946e7abc9afe13c
Feel free to fix other weird strings, too. Contributions are always welcome!
~ @npub1c7x…yhh5

2026-03-29 22:37:40 UTC

- reply

By default, all “public” repositories including code, issues, etc. can be viewed by any guest without login. Why would you want a user to require signing in without the right to comment, etc.?
~ @npub1c7x…yhh5

2026-03-10 20:53:16 UTC

The #Forgejo monthly report was published ✨

Forgejo was present at FOSDEM. The Forgejo runner received multiple bug fixes and new features. The helm chart received two minor changes. Improvements were made to the infrastructure.
https://forgejo.org/2026-02-monthly-report

2026-03-09 08:41:54 UTC

#Forgejo 14.0.3 and 11.0.11 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2026-03-02 07:58:04 UTC

- reply

Merci beaucoup !
~ @npub1c7x…yhh5

2026-02-28 16:28:37 UTC

- reply

Great that you managed! Do you want to share your experience and “delicate” steps here? https://codeberg.org/forgejo/discussions/issues/397
~ @npub1c7x…yhh5

2026-02-19 18:34:35 UTC

- reply

Thanks for sharing! Feel free to add your solution to the list of pages in the delightful list https://codeberg.org/forgejo-contrib/delightful-forgejo#pages
~ @npub1c7x…yhh5

2026-02-19 08:06:00 UTC

- reply

Some hints for customization you may find also here: https://forgejo.org/docs/latest/admin/advanced/customization/. You may take some inspiration from @npub1fh7…ee83's modifications here: https://codeberg.org/codeberg-infrastructure/forgejo/. On top of that, there were some attempts of more customization documentation within Forgejo here, but they never got merged: https://codeberg.org/forgejo/docs/pulls/1016
~ @npub1c7x…yhh5

2026-02-16 10:43:41 UTC

- reply

That is one of Forgejo's long-time goals, which is actively worked on. See https://forgejo.org/faq/#what-about-forge-federation and https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md for the current status.
~ @npub1c7x…yhh5

2026-02-16 10:00:42 UTC

- reply

Since version 12, Forgejo supports preview of 3D gLTF models, and this may be extended to other models …
https://forgejo.org/2025-07-release-v12-0/#gltf-viewer
But, for your usecase, it looks like that @npub1wfk…zv38 may indeed be the better choice.
~ @npub1c7x…yhh5

2026-02-16 09:46:54 UTC

- reply

If the deletion is a repository deletion, nothing will happen, but the mirror will continue trying to mirror, but fail. But, if the deletion is via git force push with a new git history on the same repository, this deletion will be propagated.
~ @npub1c7x…yhh5

2026-02-14 19:14:40 UTC

- reply

There is Renovate (https://docs.renovatebot.com/) which has support for forgejo: https://docs.renovatebot.com/modules/platform/forgejo/
Maybe this is what you are searching for?
~ @npub16tr…5d24

2026-02-05 15:16:09 UTC

- reply

Indeed, this is not supported, but you might checkout https://codeberg.org/forgejo/discussions/issues/397. Feel free to share your experience there, too.
~ @npub1c7x…yhh5

2026-02-04 19:31:19 UTC

- reply

There are no official Forgejo groups on Telegram.
Forgejo only has official groups on Matrix. The main Forgejo chat room is #forgejo-chat:matrix.org (the space with all rooms is #forgejo:matrix.org).
~ @npub16tr…5d24

2026-02-03 20:43:15 UTC

- reply

The https://v15.next.forgejo.org/ instance updates daily to the latest commit on the development branch. You can experiment with it there or set up a local instance. Experimental daily builds can be found here: https://codeberg.org/forgejo-experimental/forgejo/releases
~ @npub16tr…5d24

2026-02-02 08:01:16 UTC

- reply

The issue seems quite popular, but it needs someone to do the design work and implementation. Contributions are welcome (not only for this issue)!
~ @npub1c7x…yhh5

2026-01-31 14:27:13 UTC

- reply

On the download page (https://forgejo.org/download/#installation-from-binary), under "Verify GPG signature," you can find our GPG key.
The release is signed using a subkey (with a one-year expiration time) from the master key.
More information can be found here: https://forgejo.org/docs/next/contributor/release/#release-signing-keys-management.
~ @npub16tr…5d24

2026-01-31 08:03:36 UTC

The #Forgejo monthly report was published ✨

Forgejo v14 was released on time. Some regressions were quickly escalated and fixed. A security release was published for v11 and v13.
A lot of work has been done around the runner: New features and QA.
There are ongoing discussions about improving the issue reporting workflow and the license and copyright attribution in the codebase.
Work on federation is progressing.
The website was moved to our own infrastructure.
https://forgejo.org/2026-01-monthly-report

2026-01-30 16:05:19 UTC

- reply

instance administrators also have the option of customizing the behavior or enabling/disabling this feature.
For more information check the `DEFAULT_PUSH_CREATE_PRIVATE`, `ENABLE_PUSH_CREATE_USER` and `ENABLE_PUSH_CREATE_ORG` settings in the configuration file.
https://forgejo.org/docs/latest/admin/config-cheat-sheet/#repository-repository
~ @npub16tr…5d24

2026-01-30 00:20:08 UTC

- reply

Yes, it sounds also weird to me. Feel free to propose a change to the docs, if you want (Edit on bottom of the page leads to the source). ~ [@mahlzahn](https://nerdculture.de/@mahlzahn )

2026-01-29 18:37:55 UTC

- reply

If you want more security by giving access only to one repository and maybe restrict it to reading, you can use deploy keys. They aren't very well documented currently, but basically you have to add a private SSH key as an action secret to the repository from which you want to deploy, and the public counterpart to the private goal repository. Some docs about these deploy keys (in another context) you find here: https://forgejo.org/docs/latest/user/repo-mirror/#mirror-via-ssh
~ [@mahlzahn](https://nerdculture.de/@mahlzahn )

2026-01-29 18:36:25 UTC

- reply

You may use the checkout action. Likely, you'll need to use another user-wide access token for the private repositories.
https://code.forgejo.org/actions/checkout/#checkout-multiple-repos-private
~ [@mahlzahn](https://nerdculture.de/@mahlzahn )

2026-01-29 08:54:51 UTC

#Forgejo 14.0.2 was just released!
We recommend that all installations are upgraded to the latest version.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2026-01-24 11:12:26 UTC

- reply

Check out also the open feature request for generic webhooks, https://codeberg.org/forgejo/forgejo/issues/4260, and the documented workaround by @npub1p09…m5vl: https://kitten.small-web.org/reference/#webhook
~ @npub1c7x…yhh5

2026-01-24 09:00:04 UTC

- reply

I remember that someone, here in the Fediverse, posted about their working set-up, a while ago. I think it was using webhooks for that. https://forgejo.org/docs/latest/user/webhooks/
~ @npub1c7x…yhh5

2026-01-22 21:03:38 UTC

- reply

The addition should be blocked if the key is not valid. If you can reproduce this, please open an issue at https://codeberg.org/forgejo/forgejo
~ @npub16tr…5d24

2026-01-19 23:54:36 UTC

- reply

You may find an audio sample on our website ;)
https://forgejo.org/faq/#where-does-the-name-come-from
~ @npub1c7x…yhh5

2026-01-17 07:20:43 UTC

- reply

The issues addressed by this Go update do not pose any risk to the system or data security of Forgejo deployments, only potential for denial of service attacks.

2026-01-17 07:20:36 UTC

#Forgejo 11.0.10, 13.0.5 and 14.0.1 were just released!
All of them use an upgraded Go version with security fixes. We recommend that all installations are upgraded to the latest version as soon as possible.
Additionally, 14.0.1 includes a fix for a regression discovered in 14.0.0
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2026-01-15 14:09:33 UTC

#Forgejo 14.0.0 was just released!
Issues search now has inline filters. Web file editor was replaced with CodeMirror. CSRF protection is now stateless. Forgejo actions gained new features and better trust management. Foreign keys are now supported to ensure database consistency.
Check out the blog post at https://forgejo.org/2026-01-release-v14-0/
#forgejorelease

2026-01-08 11:20:58 UTC

#Forgejo 13.0.4 and 11.0.9 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2026-01-06 10:49:08 UTC

Some of us took a few days off between the years, but preparations for v14 are ongoing.
Therefore, we decided to skip the monthly report for December.
Nevertheless, you can look forward to the v14 release. Release preparations are actively underway and the release is scheduled for 15 January. If you want to help improve the release, feel free to test it. You can find more information here: https://forgejo.org/2025-09-monthly-report/#forgejo-v1300-release-candidates
The monthly report will return in early February, covering January and December.

2026-01-04 07:35:33 UTC

- reply

You may give renovate a try, in the Forgejo development it is used for the dependency management with Forgejo.
https://www.mend.io/renovate/

2025-12-02 16:36:34 UTC

The monthly report for November was just published! ✨ https://forgejo.org/2025-11-monthly-report/

A security release was published for Forgejo v13 and v11 LTS.
There is another way to report accessibility issues that lowers the barrier. User research is still seeking your help.
A lot of work has been done regarding federation, and the Dutch government has expressed interest in Forgejo.

2025-11-25 18:07:32 UTC

- reply

Work is ongoing towards federated search across instances. See https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md#federated-repo-search-discovery-wip
That may allow to search within each federated instance for repositories on other federated instances.
~ @npub1c7x…yhh5

2025-11-25 17:27:22 UTC

- reply

What is this search supposed to be searching for? Forgejo has code search, issue search, repo search, etc.
~ @npub1c7x…yhh5

2025-11-21 12:56:50 UTC

#Forgejo 13.0.3 and 11.0.8 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-11-16 08:07:07 UTC

- reply

The next stable version release is planned for 16 January 2026 [1]. Security releases are announced as issues in a dedicated repository [2]. Next security release was rescheduled to 21 November to include security patches to dependencies.
[1] https://forgejo.org/docs/latest/admin/release-schedule/
[2] https://codeberg.org/forgejo/security-announcements/issues
~ @npub1c7x…yhh5

2025-11-08 13:04:46 UTC

The #Forgejo monthly report was published ✨
Forgejo is 3 years old and was made possible by over 1,930 people and and many other free projects. Forgejo v13 was released and security vulnerabilities were fixed. Forgejo-contrib incubated new projects.
https://forgejo.org/2025-10-monthly-report

2025-10-29 18:06:11 UTC

- reply

0. Backup!
1. Upgrade to latest LTS or stable release
2. Enjoy!
See https://forgejo.org/docs/latest/admin/upgrade/
~ @npub1c7x…yhh5

2025-10-29 17:00:01 UTC

Dear #Forgejo admins and users,
We are launching another series of user research interviews in the next weeks and invite you to participate. The 45-minutes interviews help us a lot to learn about your usage of Forgejo.
Visit https://cloud.splvs.net/apps/calendar/appointment/cHr5MB2PoZDp to learn more and to schedule an appointment.

2025-10-26 06:52:55 UTC

#Forgejo 13.0.2 and 11.0.7 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-10-23 07:47:56 UTC

- reply

Codeberg has a small collection of user-contributed workflows for different needs:
https://codeberg.org/actions/meta/issues/10
And worth a look are the workflows used within Forgejo, e.g.,
https://codeberg.org/forgejo/forgejo/src/branch/forgejo/.forgejo/workflows
https://codeberg.org/forgejo/docs/src/branch/next/.forgejo/workflows
~ @npub1c7x…yhh5

2025-10-21 13:00:04 UTC

Dear #Forgejo admins,
Planning to upgrade to Forgejo v13.0 soon? Join our upgrade party and upgrade together, get help from Forgejo contributors, and get to know the community.
Today, 21 October at 16:00 UTC (18:00 CEST). See https://codeberg.org/forgejo/discussions/issues/402 for details.

2025-10-17 19:03:00 UTC

#Forgejo 13.0.1 was just released!
We recommend that all installations are upgraded to the latest version. The v13.0.0 release revealed a bug that has been in the codebase for years and caused the corruption of the Forgejo Actions secrets on instances using PostgreSQL.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-10-17 07:47:54 UTC

⚠️ Wait for Forgejo v13.0.1 to be released, do not migrate to Forgejo v13.0.0 ⚠️
A bug that could remove part of the Forgejo Actions secrets or make some of them unusable during the migration was discovered.
It will be fixed in Forgejo v13.0.1. If you already migrated, please follow the instructions from the updated release notes.
https://codeberg.org/forgejo/forgejo/milestone/21377

2025-10-16 13:59:52 UTC

#Forgejo 13.0.0 was just released!
A new moderation tool is available to report inappropriate user behavior or content that should be looked at by instance administrators. Two factor authentication (TOTP, etc.) can be enforced on the entire instance for all users or instance administrators. Forgejo Actions usability was improved with static checking of workflow files and access to the logs of all run attempts.
Check out the blog post at https://forgejo.org/2025-10-release-v13-0/
#forgejorelease

2025-10-10 08:25:16 UTC

- reply

That sounds like the correct answer, you may add the filter also using the checkout action in Forgejo (and GH) action workflows.
https://code.forgejo.org/actions/checkout/src/commit/ff7abcd0c3c05ccf6adc123a8cd1fd4fb30fb493/README.md?display=source#L107-L109
~ @npub1c7x…yhh5

2025-10-10 08:16:11 UTC

- reply

You might find @Codeberg's guide on using large files with git-LFS helpful! https://docs.codeberg.org/git/using-lfs/

2025-10-02 10:22:27 UTC

The #Forgejo monthly report was published ✨
The Forgejo v13.0 branch has been cut and the release is scheduled for October 16. Please consider testing it out and sharing your feedback to help us improve it. Forgejo Runner v11 has been released and is now licensed under GPLv3+. Improvements were made to the documentation regarding the Runner setup. Work on improving and securing database interaction has begun. There is an ongoing strong enthusiasm for translating Forgejo.
https://forgejo.org/2025-09-monthly-report

2025-09-29 16:16:07 UTC

- reply

Yeah, that needs some improvement. See https://codeberg.org/forgejo/website/issues/627 (Contributions are welcome! ;) )
~ @npub1c7x…yhh5

2025-09-25 18:33:53 UTC

- reply

These jobs are executed within Forgejo. You may check them in the admin settings, if I remember well.
@npub1c7x…yhh5

2025-09-24 17:07:01 UTC

- reply

Do you have the cron task for archive cleanup enabled?
https://forgejo.org/docs/latest/admin/config-cheat-sheet/#basic-cron-tasks---enabled-by-default
~ @npub1c7x…yhh5

2025-09-20 07:22:15 UTC

#Forgejo 12.0.4 and 11.0.6 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-09-15 15:17:28 UTC

- reply

You may be interested also in our federation roadmap!
https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md
~ @npub1c7x…yhh5

2025-09-12 17:24:05 UTC

- reply

Nice and well written blog post :) You may want to add the `--sandbox` argument to the `pandoc` execution, at least if there is the possibility that external documents may be parsed.
https://pandoc.org/demo/example33/21-a-note-on-security.html
~ @npub1c7x…yhh5

2025-09-12 17:06:52 UTC

- reply

There are ongoing discussions in the Forgejo community about how to communicate in the future, but right now you can either use the matrix room, the issue tracker, or ask your question here in the fediverse tagging #Forgejo.
https://codeberg.org/forgejo/discussions/issues/375
~ @npub1c7x…yhh5

2025-09-08 15:45:50 UTC

- reply

We're happy if this is the main issue you experienced with Forgejo! You may solve this with a bookmark to our FAQ with an audio sample ;)
https://forgejo.org/faq/#where-does-the-name-come-from
~ @npub1c7x…yhh5

2025-09-06 07:11:09 UTC

#Forgejo 12.0.3 and 11.0.5 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-09-05 16:06:46 UTC

The #Forgejo monthly report was published ✨
A Forgejo security release was published, fixing nine low severity vulnerabilities. The Forgejo contributors agreed on rules for the use of AI and the documentation is nearly complete. The runner is considered secure enough to be used in production.
https://forgejo.org/2025-08-monthly-report

2025-09-01 10:34:20 UTC

- reply

You may adjust the recognised strings in `actions.SKIP_WORKFLOW_STRINGS` in your instance configuration. https://forgejo.org/docs/latest/admin/config-cheat-sheet/#actions-actions
~ @npub1c7x…yhh5

2025-09-01 09:28:01 UTC

- reply

Hi @npub187g…3chr, the navigation was only added recently and is unfortunately not yet usable on narrower devices. Thanks for submitting the bug report https://codeberg.org/forgejo/docs/issues/1414!
~ @npub1c7x…yhh5

2025-08-31 13:38:39 UTC

#Forgejo 12.0.2 and 11.0.4 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-08-04 17:03:53 UTC

The #Forgejo monthly report was published ✨
The Forgejo v12 release was on time. The runner saw significant progress, and the release tooling was improved. Discussions emerged regarding AI contributions, contributor attributions in the documentation, and the future of communication. An #NLnet grant ended, allowing time for a retrospective.
https://forgejo.org/2025-07-monthly-report

2025-07-25 11:58:31 UTC

#Forgejo 12.0.1 was just released!
We recommend that all installations are upgraded to the latest version.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-07-25 08:02:21 UTC

- reply

Hi @npub1dgu…7a4u You may find some information about hosted Forgejo instances here: https://codeberg.org/forgejo/professional-services
~ @npub1c7x…yhh5

2025-07-23 13:01:10 UTC

- reply

That should be already possible! You may set a custom list of reaction emojis with the admin setting `ui.REACTIONS` for your instance. See
https://forgejo.org/docs/latest/admin/config-cheat-sheet/#ui-ui
~ @npub1c7x…yhh5

2025-07-21 09:31:19 UTC

- reply

That looks indeed much better. Did you consider reporting it upstream in our issue tracker (or as PR)? https://codeberg.org/forgejo/forgejo
PS: the second `!important` looks like it makes the time stamps looking broken on narrow screens?
~ @npub1c7x…yhh5

2025-07-17 14:50:32 UTC

#Forgejo 12.0.0 was just released!
We recommend that all installations are upgraded to the latest version.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-07-10 13:20:05 UTC

#Forgejo 11.0.3 and 7.0.16 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-07-09 18:18:33 UTC

- reply

Did you resolve the issue? You may find some information about this migration path in our issue tracker, for example https://codeberg.org/forgejo/forgejo/issues/7638.
~ @npub1c7x…yhh5

2025-07-02 06:11:17 UTC

- reply

We work on federation. Please check out our monthly reports for more information!
https://floss.social/@forgejo/114779836118142507
~ @npub1c7x…yhh5

2025-07-01 20:21:47 UTC

The #Forgejo monthly report was published ✨
Forgejo v12.0 branch was cut on 25 June, for a planned release on 17 July. Forgejo v11.0.2 was released on 18 June, addressing several bugs. Forgejo Runner v6.4.0 introduced offline caching support.
The minimum required Git version has been bumped and the search has been improved.
There is strong enthusiasm for translating Forgejo.
User following with #ActivityPub has progressed and a new #NLnet grant has been accepted.
https://forgejo.org/2025-06-monthly-report

2025-06-18 09:53:48 UTC

#Forgejo 11.0.2 was just released!
We recommend that all installations are upgraded to the latest version.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-06-06 18:09:02 UTC

- reply

That's beautiful, thanks for sharing!
~ @npub1c7x…yhh5

2025-06-06 17:53:24 UTC

- reply

Not that I am aware of. The default settings assure that open registration servers are not that easily misused by bots or mistakes. In your case it should be safe, if I am not wrong.
~ @npub1c7x…yhh5.

2025-06-06 17:46:36 UTC

- reply

Das ist schön, dass es am Ende geklappt hat.
~ @npub1c7x…yhh5

2025-06-01 15:24:33 UTC

The #Forgejo monthly update was published ✨
Ongoing issues with the Matrix chat room were addressed by recreating the room. Users are encouraged to join the new room, as the old room is deprecated. Security updates have been released for versions v11 and v7. Progress continues on the moderation feature funded by @npub1n8y…l96n. Work on federated user activity continues, including the ability to follow Forgejo users from GoToSocial.
https://forgejo.org/2025-05-monthly-update/

2025-05-23 20:32:02 UTC

- reply

Das ist derzeit scheinbar nicht möglich. Siehe https://codeberg.org/forgejo/forgejo/issues/1686.
~ @npub1c7x…yhh5

2025-05-23 06:52:24 UTC

- reply

I'm not aware of any feature request asking for that and it seems not to work straightforward with the already implememted package registries (https://forgejo.org/docs/latest/user/packages/). Feel free to open an issue! In the meantime, maybe the upload of container files as release assets works for you?
~ @npub1c7x…yhh5

2025-05-21 17:56:23 UTC

- reply

https://data.forgejo.org/ is the default place to get actions from that can be used within CI workflows. It may in the future be a readonly and restricted inatance (to increase availability and resistance to crawlers, etc.)
~ @npub1c7x…yhh5

2025-05-21 17:49:10 UTC

- reply

Hi, I'd like to clarify a bit the confusion about the various instances of Forgejo:
1. https://codeberg.org — a public instance, run by @npub1fh7…ee83
2. https://code.forgejo.org — instance used by Forgejo contributors for development, e.g. of the Forgejo Runner
3. https://data.forgejo.org — currently points to 2.
4. https://*.next.forgejo.org/ — test instances, updated daily for supported and upcoming versions (currently v7, try=v11 and v12)
~ @npub1c7x…yhh5

2025-05-19 17:21:59 UTC

- reply

Up to 1.22 migration is straightforward and supported.
https://forgejo.org/docs/latest/admin/gitea-migration/
Some people migrated also after, see https://codeberg.org/forgejo/forgejo/issues/7638
See https://forgejo.org/compare-to-gitea/ for a comparison.
~ @npub1c7x…yhh5

2025-05-19 17:16:49 UTC

- reply

With backups, you may try to follow the path some people discussed here: https://codeberg.org/forgejo/forgejo/issues/7638
~ @npub1c7x…yhh5

2025-05-07 06:50:10 UTC

- reply

Firstly, it seems your Forgejo instance is running on 11.0.0, still. There is a security update, we announced couple of days, ago!
https://floss.social/@forgejo/114439378099522319
Secondly, do you want your server to be announced in the delightful list for Forgejo? I added an issue here: https://codeberg.org/forgejo-contrib/delightful-forgejo/issues/132
Feel free to answer here or there! Thanks.
~ @npub1c7x…yhh5

2025-05-02 17:18:50 UTC

#Forgejo 11.0.1 and 7.0.15 were just released! They are security releases.
We recommend that all installations are upgraded to the latest version as soon as possible.
Check out the release notes and download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
#forgejorelease

2025-05-02 08:58:03 UTC

- reply

The error messages are not the same, but maybe the issue is? At least on codeberg.org jobs that have spaces in their names don't run, see https://codeberg.org/actions/meta/issues/3#issuecomment-2617025
~ @npub1c7x…yhh5

2025-05-01 15:02:20 UTC

The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo is now featured on the official Git website. Forgejo v11.0 was released on 16 April following quick fixes for identified regressions. The Helm chart was updated to version 12 for compatibility. Federation work continues on HTTP signatures and following user activity. The infrastructure faced SSH connection failures and excessive crawling.
https://forgejo.org/2025-04-monthly-update/

2025-04-29 14:46:27 UTC

- reply

I know it is not beyond rtfm, but did you see the guide in our documentation at https://forgejo.org/docs/latest/admin/runner-installation/ ?
~ @npub1c7x…yhh5

2025-04-29 14:20:24 UTC

- reply

You may be interested in the #forgejoaneksajo project! See https://codeberg.org/forgejo-aneksajo/forgejo-aneksajo/wiki and also blog entries by @datalad@fosstodon,
https://blog.datalad.org/tags/forgejo/
~ @npub1c7x…yhh5

2025-04-23 17:53:03 UTC

- reply

Vielen Dank, das wird definitiv helfen, den Fehler zu finden! Ich habe hier einen Fehlerbericht angelegt: https://codeberg.org/forgejo/forgejo/issues/7614
Weißt du bei welchem repository/welcher Datei das passiert und möglicherweise welcher git blame das auslöst (gerne auch im Issue antworten)?

2025-04-22 15:48:14 UTC

- reply

Das sieht für mich kryptisch aus. Auch habe ich keinen ähnlichen Bericht im Issue-Tracker gefunden: https://codeberg.org/forgejo/forgejo/issues
~ @npub1c7x…yhh5

2025-04-16 19:43:09 UTC

#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/
#forgejorelease

2025-04-08 06:44:48 UTC

- reply

You may have a look also at Forgejo Actions. You could even add own, more powerful runnners, if needed.
https://forgejo.org/docs/latest/user/actions/
There are also runners provided by @npub1fh7…ee83, see https://codeberg.org/actions/meta/
~ @npub1c7x…yhh5

2025-04-05 11:42:17 UTC

- reply

Hi @npub1hjn…hpjm, you can find daily experimental builds at https://codeberg.org/forgejo-experimental/-/packages/container/forgejo/ To test 11.0 you'd choose one of the container versions starting with v11.

2025-04-02 09:02:52 UTC

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/

2025-03-31 20:46:21 UTC

- reply

We use it for building the forgejo.org website with Astro and Tailwind. We have two source repositories, one for documentation (https://codeberg.org/forgejo/docs) and one for the news and other website pages (https://codeberg.org/forgejo/website). The static website is automatically built on https://codeberg.org/forgejo/pages and every pull request leads to a new branch in that can be accessed directly from forgejo.codeberg.page/@pull_XYZ.
~ @npub1c7x…yhh5

2025-03-30 23:06:15 UTC

- reply

1. <package_name>@ is usually not even necessary,
2. additionally, you may append @<ref> with a branch name or tag to install a certain version, and
3. if you need more control you may have a look also at Forgejo’s internal per-owner package registry (https://forgejo.org/docs/latest/user/packages/pypi/)
~ @npub1c7x…yhh5

2025-03-23 23:57:41 UTC

- reply

It fixes a regression that was introduced in 10.0.2. See the release notes here: https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/10.0.3.md
~ @npub1c7x…yhh5