Plans for Gitea 1.19

[lunny]

Feature Description

Hi all,

Gitea v1.18.0-rc0 has been released.
We have created the release/v1.18 branch accompanied by the v1.19.0-dev tag and are now using main for 1.19 development.

Please comment here your own plans for the next release.

Important
This summary is for things you PLAN TO DO YOURSELF, not things you want other people to do.
Other comments will be hidden.

Schedule
Gitea 1.19-rc1 is currently set to be released on 2023-01-26, so in the early of January.
All new features for 1.19 should be merged until 2022-01-11 to be included in the next release.

Previous Plans

• Plans for Gitea v1.18 #20022
• Plan of Gitea v1.17 #18345
• Plan of Gitea v1.16 #16429
• Discussion of v1.15.x Roadmap #14477

Screenshots

No response

[lunny]

I would like below issues/prs could be resolved in this release.

• Add support to import repository data from an exported data of Github #18165
• An internal CI/CD system compatible with Github actions workflow yaml syntax, action yaml syntax and most action plugins #13539

[delvh]

I can directly copy my plans from 1.18, since nothing has changed about them:

---

My plans are

• Reviewing a lot of PRs (the never ending task)
• a Plugin Mechanism #20126 so that we can finally offload all the optional customizations there without bloating the main binary too much. (At least if I find the time for it, I know already that my free time will be rather scarce until the next release)

[6543]

• help with private issues ...
• help with federation - mostly reviews I guess
• refactoring stuff ...
• help long open pulls
• better integration of external CIs (define api etc ... cc @lunny )
• Project boards for organizations (Project boards / kanban: Support for organization-level boards #13405)

---

#20022 (comment)

[ivancxj]

• Proposal: Pin Issues #2175

[richmahn]

Plan to get the Git Refs API CRUD endpoints done. #21328

Plan to get a conflict resolver done. #9014

[harryzcy]

• Support scoped access tokens #20908

[ghost]

• Add option to enable CAPTCHA validation for login #21638
• Allow disable RSS/Atom feed #21622
• Allow disable sitemap #21617
• Fix button in branch list, avoid unexpected page jump before restore branch actually done #21562
• Fix UI column width, button overflow Fomantic's grid #21559
• Remove deprecated DSA host key from Docker Container #21522

[wolfogre]

• Fix bugs of parsing YAML template:
  • 
  • Support comma-delimited string as labels in issue template #21831
  • Ignore issue template with a special name #21830
• Support config.yml in ISSUE_TEMPLATE
• An internal CI/CD system compatible with Github actions workflow yaml syntax, action yaml syntax and most action plugins #13539
  • Implement actions #21937

[massimiliano-dalcero]

• Add automated project board ( [Feature] Add automated project board #14359 )
• Show in the issue list the board name
• Automation based on action on the boards (when a issue is moved to bord "XYZ" do "this")

[JakobDev]

Support config.yml in ISSUE_TEMPLATE

I've started working on this. See #20956. The PR is just for disabling blank issue. Other things should be in a separated PR.

[CodeDoctorDE]

I want to start contributing again and I'm currently working on #22273. I will look if I can do more in the future

[gnat]

• Preview images for Issue cards in Project Board view #22112

[techknowlogick]

closing and locking now that rc0 is out.