github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Plans for Gitea 1.21 #10987

New Issue
Closed
opened 2025-11-02 09:24:07 -06:00 by GiteaMirror · 17 comments
GiteaMirror commented 2025-11-02 09:24:07 -06:00
Owner
Copy Link

Originally created by @delvh on GitHub (Jun 7, 2023).

Hi all,

Gitea v1.20.0-rc0 has been released.
We have created the release/v1.20 branch accompanied by the v1.21.0-dev tag and are now using main for 1.21 development.
As always, this issue is intended to show what you can expect from the next version.

Schedule

Gitea 1.21 is currently set to enter feature freeze on , so in the beginning of september.
This deadline is at the moment only a rough estimate and might change in the future.

Previous Plans

⚠️ Important

This summary is for things you plan to implement yourself, not things you want (from other people).
Wishes and other offtopic comments will be hidden.

Originally created by @delvh on GitHub (Jun 7, 2023). Hi all, Gitea `v1.20.0-rc0` has been released. We have created the `release/v1.20` branch accompanied by the `v1.21.0-dev` tag and are now using `main` for `1.21` development. As always, this issue is intended to show what you can expect from the next version. ## Schedule Gitea `1.21` is currently set to enter feature freeze on <time datetime="2023-09-03 23:59+00:00">2023-09-03 23:59 UTC</time>, so in the beginning of september. This deadline is at the moment only a rough estimate and might change in the future. <details><summary><h2>Previous Plans</h2></summary> - #23072 - #21598 - #20022 - #18345 - #16429 - #14477 </details> ## :warning: Important This summary is for things you **plan to implement yourself**, not things you want (from other people). Wishes and other offtopic comments will be hidden.
GiteaMirror added the type/summary label 2025-11-02 09:24:07 -06:00
GiteaMirror commented 2025-11-02 09:24:08 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jun 7, 2023):

I'll start with my plans:

  • Reviewing a lot of PRs (as always)
  • Merging the separate project templates together
  • #25180
somewhere on the back of my TODO list
@delvh commented on GitHub (Jun 7, 2023): I'll start with my plans: - [x] Reviewing **a lot** of PRs ([as always](https://github.com/go-gitea/gitea/pulls?q=is%3Apr+reviewed-by%3Adelvh+milestone%3A1.20.0+)) - [x] Merging the separate project templates together - [x] #25180 <details><summary>somewhere on the back of my TODO list</summary> - [ ] #23203 - [ ] #20126 - [ ] #12640 </details>
GiteaMirror commented 2025-11-02 09:24:08 -06:00
Author
Owner
Copy Link

@jrjake commented on GitHub (Jun 8, 2023):

I'm pretty new to the codebase but I'm going to try my hand at implementing:

@jrjake commented on GitHub (Jun 8, 2023): I'm pretty new to the codebase but I'm going to try my hand at implementing: - [ ] #5512 using the [russellhaering/gosaml2](https://github.com/russellhaering/gosaml2) library - [ ] #25132 - [ ] (future patch(s) adding actual logic behind SAML authentication)
GiteaMirror commented 2025-11-02 09:24:08 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Jun 8, 2023):

  • Remove more Fomantic UI
  • Try integrating tailwind.css
  • Evaluate switching JS to TS (uncertain)
@silverwind commented on GitHub (Jun 8, 2023): - [x] Remove more Fomantic UI - [ ] Try integrating tailwind.css - [ ] Evaluate switching JS to TS (uncertain)
GiteaMirror commented 2025-11-02 09:24:08 -06:00
Author
Owner
Copy Link

@oetiker commented on GitHub (Jun 9, 2023):

@silverwind it was mentioned before, but switching to svelte, combined with tailwind might be a great way forward

@oetiker commented on GitHub (Jun 9, 2023): @silverwind it was mentioned before, but switching to svelte, combined with tailwind might be a great way forward
GiteaMirror commented 2025-11-02 09:24:09 -06:00
Author
Owner
Copy Link

@wolfogre commented on GitHub (Jun 13, 2023):

Backlog
  • Take over https://github.com/go-gitea/gitea/pull/18165
@wolfogre commented on GitHub (Jun 13, 2023): - [x] #24662 - [x] #25174 - [ ] #24603 - [ ] #24543 <details> <summary>Backlog</summary> - Take over `https://github.com/go-gitea/gitea/pull/18165` </details>
GiteaMirror commented 2025-11-02 09:24:09 -06:00
Author
Owner
Copy Link

@HesterG commented on GitHub (Jun 13, 2023):

@HesterG commented on GitHub (Jun 13, 2023): - [ ] Finish the dropdowns in action list https://github.com/go-gitea/gitea/issues/25042 - [x] Fix more issues like https://github.com/go-gitea/gitea/issues/25096 (change the form actions to form fetch to avoid duplicate requests) - [x] https://github.com/go-gitea/gitea/issues/24593 - [ ] Fix more frontend inconsistency
GiteaMirror commented 2025-11-02 09:24:09 -06:00
Author
Owner
Copy Link

@sillyguodong commented on GitHub (Jun 13, 2023):

@sillyguodong commented on GitHub (Jun 13, 2023): - [x] https://github.com/go-gitea/gitea/pull/24806 - [x] https://github.com/go-gitea/gitea/pull/24724 - [x] https://github.com/go-gitea/gitea/pull/25199 - [ ] https://github.com/go-gitea/gitea/pull/25362 - [ ] https://gitea.com/gitea/act_runner/issues/232
GiteaMirror commented 2025-11-02 09:24:09 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jun 20, 2023):

I will work on

@lunny commented on GitHub (Jun 20, 2023): I will work on - [x] #25206 - [ ] #25071 - [x] #22743 - [ ] #20549
GiteaMirror commented 2025-11-02 09:24:10 -06:00
Author
Owner
Copy Link

@denyskon commented on GitHub (Jun 20, 2023):

  • ability to hard-reset to specific commit from UI
  • more general UI/mobile enhancements
  • card element unification (use the same styles, and partially shared templates for similar card elements)
  • refactor some templates to remove duplicated code (e. g. issue list, projects, milestones)
  • review or close old PRs / issues
@denyskon commented on GitHub (Jun 20, 2023): - [ ] ability to hard-reset to specific commit from UI - [ ] more general UI/mobile enhancements - [x] card element unification (use the same styles, and partially shared templates for similar card elements) - [x] refactor some templates to remove duplicated code (e. g. issue list, projects, milestones) - [ ] review or close old PRs / issues
GiteaMirror commented 2025-11-02 09:24:10 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jun 20, 2023):

Off-topic, but:
What exactly do you mean by hard-reset to specific commit? Commit Reverting, or really a reset --hard?
Because I'm rather against a reset --hard and more in favor of reverting.
Otherwise, there's too much error potential.
Anyway, I think all this discussion should be outsourced into a new issue. We shouldn't discuss these things here.

@delvh commented on GitHub (Jun 20, 2023): Off-topic, but: What exactly do you mean by `hard-reset to specific commit`? Commit Reverting, or really a `reset --hard`? Because I'm rather against a `reset --hard` and more in favor of reverting. Otherwise, there's too much error potential. Anyway, I think all this discussion should be outsourced into a new issue. We shouldn't discuss these things here.
GiteaMirror commented 2025-11-02 09:24:10 -06:00
Author
Owner
Copy Link

@denyskon commented on GitHub (Jun 20, 2023):

Off-topic, but:
What exactly do you mean by hard-reset to specific commit? Commit Reverting, or really a reset --force?
Because I'm rather against a reset --force and more in favor of reverting.
Otherwise, there's too much error potential.
Anyway, I think all this discussion should be outsourced into a new issue. We shouldn't discuss these things here.

I'm talking about git reset --hard SHA, which just removes all commits after SHA.
Of course it's on the maintainers to decide about it. My use case is to remove the changes caused by multiple commits, so if the decision is made not to allow reset, I could also try to extend the existing revert mechanism to revert multiple commits.
But as you said, this should be moved out to a separate issue.

@denyskon commented on GitHub (Jun 20, 2023): > Off-topic, but: > What exactly do you mean by `hard-reset to specific commit`? Commit Reverting, or really a `reset --force`? > Because I'm rather against a `reset --force` and more in favor of reverting. > Otherwise, there's too much error potential. > Anyway, I think all this discussion should be outsourced into a new issue. We shouldn't discuss these things here. I'm talking about `git reset --hard SHA`, which just removes all commits after SHA. Of course it's on the maintainers to decide about it. My use case is to remove the changes caused by multiple commits, so if the decision is made not to allow reset, I could also try to extend the existing revert mechanism to revert multiple commits. But as you said, this should be moved out to a separate issue.
GiteaMirror commented 2025-11-02 09:24:10 -06:00
Author
Owner
Copy Link

@prologic commented on GitHub (Jun 24, 2023):

I'm pretty new to the codebase but I'm going to try my hand at implementing:

Please let me know if this is inappropriate to comment/contribute...

Could we look at implementing Trusted Header / Proxy Auth first? That way some folks can very easily and cheaply implement SSO with things like Authelia

@prologic commented on GitHub (Jun 24, 2023): > I'm pretty new to the codebase but I'm going to try my hand at implementing: > > * [ ] [Support SAML 2.0 as Login-Source (Service Provider) #5512](https://github.com/go-gitea/gitea/issues/5512) using the [russellhaering/gosaml2](https://github.com/russellhaering/gosaml2) library > > * [ ] [Enable configuration of SAML authentication sources (#5512) #25132](https://github.com/go-gitea/gitea/pull/25132) > * [ ] (future patch(s) adding actual logic behind SAML authentication) Please let me know if this is inappropriate to comment/contribute... Could we look at implementing Trusted Header / Proxy Auth first? That way some folks can very easily and cheaply implement SSO with things like Authelia
GiteaMirror commented 2025-11-02 09:24:11 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jun 24, 2023):

@prologic that is already possible. search for reverse_proxy_auth in the cheat sheet and that'll be a starting point that works.

@techknowlogick commented on GitHub (Jun 24, 2023): @prologic that is already possible. search for reverse_proxy_auth in the cheat sheet and that'll be a starting point that works.
GiteaMirror commented 2025-11-02 09:24:11 -06:00
Author
Owner
Copy Link

@ivancxj commented on GitHub (Jul 4, 2023):

Enhance issues and project management
Make gitea a one-stop collaboration platform for development，full Lifecycle support of team collaboration and product development，like https://www.tapd.cn

@ivancxj commented on GitHub (Jul 4, 2023): Enhance issues and project management Make gitea a one-stop collaboration platform for development，full Lifecycle support of team collaboration and product development，like https://www.tapd.cn
GiteaMirror commented 2025-11-02 09:24:11 -06:00
Author
Owner
Copy Link

@editfund-founder commented on GitHub (Jul 8, 2023):

https://primer.style/css/

@editfund-founder commented on GitHub (Jul 8, 2023): https://primer.style/css/
GiteaMirror commented 2025-11-02 09:24:11 -06:00
Author
Owner
Copy Link

@puni9869 commented on GitHub (Aug 26, 2023):

I am currently working on

@puni9869 commented on GitHub (Aug 26, 2023): I am currently working on * [ ] `WIP` Feature https://github.com/go-gitea/gitea/issues/25237 * [x] Feature https://github.com/go-gitea/gitea/pull/26151 * [x] https://github.com/go-gitea/gitea/pull/26212 * [x] More pr review * [x] Fix mobile view ports.
GiteaMirror commented 2025-11-02 09:24:11 -06:00
Author
Owner
Copy Link

@denyskon commented on GitHub (Sep 22, 2023):

Closing as 1.21rc0 released, replaced by #27194 :)

@denyskon commented on GitHub (Sep 22, 2023): Closing as 1.21rc0 released, replaced by #27194 :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/summary
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10987
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?