implement projects/comments/issues as files in the git repository #14724

New Issue

GiteaMirror · 2025-11-02T11:21:16-06:00

GiteaMirror commented

2025-11-02 11:21:16 -06:00

Originally created by @printfdebugging on GitHub (Jul 8, 2025).

Feature Description

currently the project/comment/issues live with the git server one is using and if some day the service provider decides to stop providing services, the users either have to look for migration options or just have to say goodby to their beloved issues/comments/projects.

it would be good if these are stored in the same git repository in separate branches as files as then one wouldn't have to worry about them cluttering the commit history but at the same time they would truely own everything in the repository.

Screenshots

No response

Originally created by @printfdebugging on GitHub (Jul 8, 2025). ### Feature Description currently the project/comment/issues live with the git server one is using and if some day the service provider decides to stop providing services, the users either have to look for migration options or just have to say goodby to their beloved issues/comments/projects. it would be good if these are stored in the same git repository in separate branches as files as then one wouldn't have to worry about them cluttering the commit history but at the same time they would truely own everything in the repository. ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 11:21:16 -06:00

GiteaMirror closed this issue

2025-11-02 11:21:16 -06:00

GiteaMirror commented

2025-11-02 11:21:17 -06:00

@wxiaoguang commented on GitHub (Jul 8, 2025):

IIRC there were some similar feature requests before (many years ago), but I think it's not feasible nowadays, because many operations are heavily database-based, it's almost impossible to store the data in files.

@wxiaoguang commented on GitHub (Jul 8, 2025): IIRC there were some similar feature requests before (many years ago), but I think it's not feasible nowadays, because many operations are heavily database-based, it's almost impossible to store the data in files.

GiteaMirror commented

2025-11-02 11:21:18 -06:00

@printfdebugging commented on GitHub (Jul 8, 2025):

how so? i see that the comments are plain text, the content uploaded like videos or audios can be stored in a folder something like .git/issues/142/ along with the rest of the information. it would be like gtimelog entries but much more nicely ordered with jinja like format spaces to be filled in by git.

@printfdebugging commented on GitHub (Jul 8, 2025): how so? i see that the comments are plain text, the content uploaded like videos or audios can be stored in a folder something like .git/issues/142/ along with the rest of the information. it would be like gtimelog entries but much more nicely ordered with jinja like format spaces to be filled in by git.

GiteaMirror commented

2025-11-02 11:21:18 -06:00

@wxiaoguang commented on GitHub (Jul 8, 2025):

Issue search, filter, labels, permission, edit history, etc, all the operations are database-based, the code has been written so.

If you need to use git to store projects/comments/issues, you can use a 3rdparty app/tool which is designed to work that way.

@wxiaoguang commented on GitHub (Jul 8, 2025): Issue search, filter, labels, permission, edit history, etc, all the operations are database-based, the code has been written so. If you need to use git to store projects/comments/issues, you can use a 3rdparty app/tool which is designed to work that way.

GiteaMirror commented

2025-11-02 11:21:18 -06:00

@printfdebugging commented on GitHub (Jul 8, 2025):

i understand, i will write to git mailing list to see if i get some response from them, maybe if git supports this by default then the hosting service providers would also be willing to provide a frontend for it, otherwise expecting them to do everything seems like asking too much for almost no reason.

@printfdebugging commented on GitHub (Jul 8, 2025): i understand, i will write to git mailing list to see if i get some response from them, maybe if git supports this by default then the hosting service providers would also be willing to provide a frontend for it, otherwise expecting them to do everything seems like asking too much for almost no reason.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14724