gitea/blog
44
20
Fork 31
Code Issues 10 Pull Requests 1 Actions Activity

Blog for Gitea 1.17.0 #199

Merged
6543 merged 9 commits from :release-1.17.0 into master 2022-07-31 12:23:46 +00:00
Conversation 3 Commits 9 Files Changed 7 +6 -6
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 43c0c3aebb - Show all commits

12
content/post/release-of-1.17.0.md
View File

@ -74,33 +74,33 @@ Note that this feature will only be enabled when the target branch has branch pr
|-|-|
| ![screenshot 1](/demos/19648/1.png) | ![screenshot 2](/demos/19648/2.png) |
### Allow edits by maintainers ([#18002](https://github.com/go-gitea/gitea/pull/18002))
### :rocket: Allow edits by maintainers ([#18002](https://github.com/go-gitea/gitea/pull/18002))
Thanks to [@qwerty287](https://github.com/qwerty287), Gitea now allows you to decide if maintainers of the upstream
repository can push to the head branch of your PR when creating a Pull Request from a fork.
This enables a workflow similar to how Gitea itself is maintained currently and can simplify the PR workflow for open source development.
### Permanent issue (and PR) deletion ([#19032](https://github.com/go-gitea/gitea/pull/19032))
### :rocket: Permanent issue (and PR) deletion ([#19032](https://github.com/go-gitea/gitea/pull/19032))
Thanks to [@fnetX](https://codeberg.org/fnetX), to combat spam and confidential information, issues (and subsequently PRs) can now be permanently deleted.
A repository admin or instance admin can find the delete button at the bottom of the sidebar of the issue or pull reuqest.
### Generate table of contents in wikis ([#19873](https://github.com/go-gitea/gitea/pull/19873))
### :rocket: Generate table of contents in wikis ([#19873](https://github.com/go-gitea/gitea/pull/19873))
Thanks to [@zeripath](https://github.com/zeripath), wiki pages now show their logical structure automatically in the sidebar. This removes the need to manually maintain a ToC and helps you to skim for the most important sections.
### Customizing the default commit messages ([#18177](https://github.com/go-gitea/gitea/pull/18177))
### :rocket: Customizing the default commit messages ([#18177](https://github.com/go-gitea/gitea/pull/18177))
Thanks to [@lunny](https://github.com/lunny), you can now set the default merge message used for merging PRs.
The customization files must be in `.gitea/default_merge_message/<uppercase_merge_style>_TEMPLATE.md`.
More information on the file names and possible variables can be found [here](https://docs.gitea.io/en-us/issue-pull-request-templates/).
noerw marked this conversation as resolved Outdated
Gusted commented 2022-07-30 21:55:00 +00:00
Outdated
Review
Copy Link

Agree on removing.

Agree on removing.
### Keeping the original ID of issues ([#18446](https://github.com/go-gitea/gitea/pull/18446))
### :rocket: Keeping the original ID of issues ([#18446](https://github.com/go-gitea/gitea/pull/18446))
When you migrate a repository including its issues, their original ID will be persisted.
This is only the first step to allow complete mirroring of issues and Pull Requests from other (Gitea, GitHub, GitLab, ...) instances, with more to come in later releases.
### Federation Progress ([#19561](https://github.com/go-gitea/gitea/pull/19561) & [#19462](https://github.com/go-gitea/gitea/pull/19462))
### :rocket: Federation Progress ([#19561](https://github.com/go-gitea/gitea/pull/19561) & [#19462](https://github.com/go-gitea/gitea/pull/19462))
Gitea 1.17 lays the foundation to allow instances to communicate with each other in the future:
A new API path to allow basic communication of statistics between each other was added ([#19561](https://github.com/go-gitea/gitea/pull/19561)).