mirror of
https://gitea.com/gitea/blog.git
synced 2024-06-02 04:11:23 +05:30
chore: nits and structure thanks
Signed-off-by: jolheiser <john.olheiser@gmail.com>
This commit is contained in:
parent
b6c6f569c7
commit
d05d4f3c11
|
@ -17,21 +17,18 @@ We highly encourage users to update to this version for many new features and ot
|
|||
|
||||
We have merged [544](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+milestone%3A1.19.0+is%3Amerged) pull requests to release this version.
|
||||
|
||||
<!-- Security Thanks! -->
|
||||
## Thank you!
|
||||
|
||||
We would like to thank the [Blender team](https://blender.org) for their extensive work on this version, i.e. through issues, pull requests, and support of the Gitea Project.
|
||||
- The [Blender team](https://blender.org) for their extensive work on this version, i.e. through issues, pull requests, and support of the Gitea Project.
|
||||
- [@wxiaoguang](https://gitea.com/wxiaoguang), [@fsologureng](https://codeberg.org/fsologureng), and everyone else who has been helping with the accessibility changes.
|
||||
- [@yardenshoham](https://gitea.com/yardenshoham) for his contribution on [Gitea Backporter](https://github.com/GiteaBot/gitea-backporter), which makes our backport work significantly easier than before.
|
||||
- [@pat-s](https://gitea.com/pat-s) for his work to make static website PRs previewable.
|
||||
|
||||
Another thank you is in order for [@wxiaoguang](https://gitea.com/wxiaoguang), [@fsologureng](https://codeberg.org/fsologureng), and everyone else who has been helping with the accessibility changes.
|
||||
|
||||
We also thank [@yardenshoham](https://gitea.com/yardenshoham) for his contribution on [Gitea Backporter](https://github.com/GiteaBot/gitea-backporter) which made our backport work significantly easier than before.
|
||||
|
||||
Thank [@pat-s](https://gitea.com/pat-s) for his work to make static websites PRs previewable.
|
||||
We would also like to thank all of our supporters on [Open Collective](https://opencollective.com/gitea) who are helping to sustain us financially.
|
||||
|
||||
You can download one of our pre-built binaries from our [downloads page](https://dl.gitea.com/gitea/1.19.0/) - make sure to select the correct platform! For further details on how to install, follow our [installation guide](https://docs.gitea.io/en-us/install-from-binary/).
|
||||
|
||||
We are now working on moving our infrastructure from `gitea.io` to `gitea.com`, as well as migrating from Drone CI to Gitea Actions. During this conversion, if you encounter any problem, please report them via [discord](https://discord.gg/gitea).
|
||||
|
||||
We would also like to thank all of our supporters on [Open Collective](https://opencollective.com/gitea) who are helping to sustain us financially.
|
||||
We are now working on moving our infrastructure from `gitea.io` to `gitea.com`, as well as migrating from Drone CI to Gitea Actions. During this conversion, if you encounter any problems, please report them via [discord](https://discord.gg/gitea).
|
||||
|
||||
**Have you heard? We now have a [swag shop](https://shop.gitea.io)! :shirt: :tea:**
|
||||
|
||||
|
@ -159,7 +156,7 @@ Gitea 1.19 ships with three new package registries that coincidentally all start
|
|||
|
||||
Furthermore, it is now possible to limit how large an uploaded package can be, or when packages will be deleted again to save space.
|
||||
|
||||
Thanks to [@KN4CK3R](https://gitea.com/KN4CK3R) for all of their work adding each new package registry types and restricting the amount of space consumed by packages.
|
||||
Thanks to [@KN4CK3R](https://gitea.com/KN4CK3R) for all of his work adding each of the new package registry types and restricting the amount of space consumed by packages.
|
||||
|
||||
### :rocket: Citing repos ([#19999](https://github.com/go-gitea/gitea/issues/19999))
|
||||
Repositories with a `CITATION.cff` file will now automatically display a hint to cite the repository.
|
||||
|
@ -178,7 +175,7 @@ Thanks to [@yardenshoham](https://github.com/yardenshoham)
|
|||
Now we provide official pre-built FreeBSD binaries.
|
||||
|
||||
Thanks to [techknowlogick](https://gitea.com/techknowlogick) for the many year effort of adding
|
||||
freebsd support to XGO, and to the FreeBSD community for their advice throuough the process
|
||||
FreeBSD support to XGO, and to the FreeBSD community for their advice throuough the process
|
||||
|
||||
### :rocket: Highlight `Note` and `Warning` in markdown quotes ([#21711](https://github.com/go-gitea/gitea/issues/21711))
|
||||
The first `**Note**` or `**Warning**` found in a markdown quote (`> text`) will automatically be highlighted now:
|
||||
|
@ -194,7 +191,7 @@ Thanks to [@zeripath](https://github.com/zeripath)
|
|||
|
||||
### :rocket: Projects for organizations/users ([#22235](https://github.com/go-gitea/gitea/issues/22235))
|
||||
If you have ever had at least two repositories that were related to each other, you probably hated working with projects.
|
||||
This has now improved tremendously as Gitea 1.19 allows to define projects on a "global" level, to track work in multiple repositories.
|
||||
This has now improved tremendously as Gitea 1.19 allows you to define projects on a "global" level, to track work in multiple repositories.
|
||||
|
||||
![org-user projects](/demos/22235/Org-User-level-projects.png)
|
||||
|
||||
|
@ -227,10 +224,10 @@ By the way, the labels you can see in the screenshot are part of the new label s
|
|||
It mimics the labels Gitea uses for its own development.
|
||||
Read more about (scoped) labels in the [documentation](https://docs.gitea.io/en-us/labels/#scoped-labels).
|
||||
|
||||
Thanks to [@brechtvl](https://github.com/brechtvl) and the rest of the blender team for adding this functionality to Gitea
|
||||
Thanks to [@brechtvl](https://github.com/brechtvl) and the rest of the Blender team for adding this functionality to Gitea
|
||||
|
||||
### :rocket: Secrets ([#22142](https://github.com/go-gitea/gitea/issues/22142))
|
||||
Both repos, users and organizations can now store secrets that can be used for example inside Gitea actions.
|
||||
Repos, users and organizations can now store secrets that can be used for example inside Gitea actions.
|
||||
These secrets cannot be seen by anyone who isn't an owner of the repo or organization.
|
||||
|
||||
Thanks to [@wolfogre](https://gitea.com/wolfogre), [@lunny](https://gitea.com/lunny) and [@lafriks](https://gitea.com/lafriks)
|
||||
|
|
Loading…
Reference in a new issue