Versioning: Gitea 1.19 allows using GitHub Actions
Version 1.19 of the Gitea version management tool comes with a built-in system for Continuous Integration (CI) as a preview: Gitea Actions. In addition, the minor release makes it easier to copy the entire contents of a file Note– and Warning-Colors hints in Markdown block quotes and can handle Asciicast files. A total of 544 pull requests flowed into the new version.
Gitea is a Git service written in Go and available open source as a community-led successor to Gogs. It is intended to make it easy for developers to run a Git service on their own servers. A tabular list shows the Gitea features in comparison with other version management tools such as GitHub, GitLab or BitBucket.
Continuous integration with Gitea Actions
First introduced in 2019, GitHub Actions are a CI/CD (Continuous Integration/Continuous Delivery) designed part of the version control service GitHub. According to the Gitea team, the CI/CD integration was one of the most requested feature requests, which it has now complied with: The new integrated CI system Gitea Actions is included as a preview. It allows reusing known workflows and using GitHub Actions in self-managed Gitea instances.
Currently not fully compatible with GitHub Actions, the development team plans to increase compatibility in upcoming releases. With the introduction of Gitea Actions comes the non-backwards compatible change that the username gitea-actions is reserved for it. If a user with such a name exists, the admin has to rename it, which can be done using the admin panel.
Gitea 1.19: Thanks to Gitea Actions, workflows can be executed automatically after a corresponding trigger.
(Image: Gitea)
A tutorial for using Gitea Actions can be found on the Gitea blog. The GitHub issue provides further background information, in which the two years of work can be tracked.
The announced blog entry highlights further highlights in Gitea 1.19.
(May)
