Gitea 1.24 adds enforced Git configs, 2FA mandate, enhanced anonymous repo access

Gitea 1.24.0 enforces GIT_CONFIG_NOSYSTEM=1, making the app ignore /etc/gitconfig and use only its internal config at {AppDataPath}/home/.gitconfig. Users must migrate any relevant settings accordingly. Additionally, administrators can require two-factor authentication (2FA) for all users via the new security.TWO_FACTOR_AUTH setting; users without 2FA can only browse but not interact with repositories via web or API.

Private and unlisted repositories now support anonymous access to code, issues, and wikis. File browsing is improved with a new file tree and Material icons as the default (configurable). Users committing via the web UI can now choose from multiple email addresses. Organizations also gain support for dual README repositories: a public .profile and a private .profile-private.

The release adds enhanced API support for managing artifacts and registering runners for CI workflows. Issues can now be sorted by priority using exclusive labels, and project kanban boards feature a new fullscreen mode. Organization-level worktime reporting is now available, with filters by time, repo, milestone, and member. You can read more about the changes in the official changelog.