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

[feat] modern editor friendly config file #14771

New Issue
Open
opened 2025-11-02 11:22:36 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 11:22:36 -06:00
Owner
Copy Link

Originally created by @loynoir on GitHub (Jul 17, 2025).

Feature Description

problem

app.ini cannot benefit from editor tab-completion and validation.

feat

  • support gitea.jsonc or gitea.yml

  • generate json schema and publish to schema store

related

https://github.com/microsoft/vcpkg/issues/34706

Screenshots

No response

Originally created by @loynoir on GitHub (Jul 17, 2025). ### Feature Description ## problem `app.ini` cannot benefit from editor tab-completion and validation. ## feat - support `gitea.jsonc` or `gitea.yml` - generate json schema and publish to schema store ## related https://github.com/microsoft/vcpkg/issues/34706 ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 11:22:36 -06:00
GiteaMirror commented 2025-11-02 11:22:36 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Jul 17, 2025):

YAML sound fine to me. And yes, schemastore support would be nice to enable editor highlighting. We could validate config schema on startup and issue warnings in log and admin pages if there's a schema mismatch.

I think what also would need to be provided is a config migration tool that converts ini to yaml.

@silverwind commented on GitHub (Jul 17, 2025): YAML sound fine to me. And yes, schemastore support would be nice to enable editor highlighting. We could validate config schema on startup and issue warnings in log and admin pages if there's a schema mismatch. I think what also would need to be provided is a config migration tool that converts ini to yaml.
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/proposal
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#14771
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?