The release of the collaborative development platform Forgejo 13.0 has been announced, allowing users to deploy a system for collaboration with Git repositories, similar to the solutions provided by GitHub, Bitbucket, and Gitlab. Forgejo is a fork of the Gitea project, which itself branched off from the Gogs platform. The separation of Forgejo occurred in 2022 after attempts to commercialize Gitea and the management transitioning to a commercial company. The Forgejo project adheres to principles of independent governance and community oversight. The Git hosting service Codeberg.org has transitioned to Forgejo. The project code is written in Go and is distributed under the GPLv3 license.
Key features of the platform include low resource consumption (can run on a Raspberry Pi or inexpensive devices) VPS) and a simple installation process. Typical project management capabilities are provided, such as task management, issue tracking, pull requests, wikis, tools for coordinating developer teams, release preparation, automation of package deployment in repositories, access rights management, integration with continuous integration platforms, code search, authentication via LDAP and OAuth, repository access via SSH and HTTP/HTTPS protocols, webhooks integration for services like Slack, Discord, and others, support for Git hooks and Git LFS, migration and mirroring tools for repositories. Notably, it supports the ActivityPub protocol for connecting individual servers developers in a federated network.
Key Changes:
- New features have been added to inform administrators of publicly accessible servers about violations of rules and the placement of unwanted content. Complaints can be directed against users, organizations, repositories, pull requests, issue reports, and comments.
After submitting a complaint, it appears in a separate section of the administrator interface. Repeated complaints are grouped and sorted in the overall list by the number of notifications sent by various participants.
- An interface has been added for migrating projects from the Pagure collaborative development system, which can be used to transfer projects to the newly launched Fedora Forge collaborative development service, developed to replace the Pagure platform used in Fedora for collaboration on code and package metadata.
- A setting has been added: '[security].GLOBAL_TWO_FACTOR_REQUIREMENT', which mandates the use of two-factor authentication for users or administrators, for example, based on one-time passwords (TOTP).
- Metadata EXIF is being removed from image files uploaded as user avatars or pictures in repositories. This cleaning helps prevent the leakage of sensitive data, such as location and device information. A command 'forgejo doctor avatar-strip-exif' has been proposed for removing EXIF metadata from previously uploaded images.
- The ability to view the log of past attempts to run Actions handlers has been added.
- The web interface now supports static analysis of files with action handlers for early detection of common typos and errors, such as using a handler in the wrong context.
- When forcing a push request, information about the build status of all commits in the continuous integration environment is now displayed.
- The Markdown text editor now includes keyboard shortcuts for bold (Ctrl+B) and italic (Ctrl+I) formatting for selected text.
- Loading time for applications related to the release, such as compiled binaries, is now shown.
- The commit list now displays tags associated with commits.
Source: opennet.ru
