Supporting distributed (repo contained) issues and pull requests

[hoijui]

Why

I think repo hosted issues and pull requests are absolutely the way to go, as it allows for really distributed and self-contained repos/projects, that can be fully backed up or migrated to a different host with a git clone. One can also work on them fully offline.

What

There are already some projects supporting in-repo issues. They use different storage models, for example:

• each issue is a file in the branch it concerns
• each issue is metadata in a commit
• all issues are in a separate branch
• each issue is a branch
• ...

The user usually interacts with it in one of two ways:

• using a cmd-line (native) client
• using a web-based GUI (either remote or locally hosted)

Conclusion

If Gitea supported storing issues and pull requests directly in the repo itsself, with the same web-interface it uses for its current issues and pull requests, that would be a game changer for this self-contained meta-info, as it would suddenly become very practically viable. I would also consider it a huge advantage of gitea over github and gitlab.

This is a feature request, and I can not even give a suggestion for which model/software to use for it in the background, or whether to support multiple back-ends, or whether to evne develop a new model. I would just like to have a discussion about it.

[typeless]

Just found this https://github.com/MichaelMure/git-bug/

[mei-rune]

good idea.

[wrenix]

yes a offline usage would be nice

[bqv]

+1