-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Merge docs into this repo #2865
Comments
docker yml also need to be updated so that docs site is updated from main repository |
Thanks for your suggestion. Here's my opinion: I kind of like the idea for small projects. But Gitea is big and is cleaner to have code/issues/PRs separated IMHO. Also, some Gitea users may not know Go, but may like to contribute to docs. They currently don't need to clone 5,700+ commits to do it.
With Git Subtrees would be possible to merge the repos preserving the history. |
Idea for moving docs to main repo is to be able submit documentation together with updated code otherwise docs stay out of date |
So maybe send docs commit from docs repo to gitea repo via giteabot when commit pushed to CI. We almost declaim docs repo and docs.gitea.io keep the latest documents. And you can find history docs on your gitea instance |
For me target is to get docs updated when new features are implemented and having it other repository just gets into way as nobody is willing to submit other PR to update docs |
Thinking about this now, I probably don't need to bring history over as when PRs are accepted they are squashed to that history would be lost anyway. So I'll submit a PR with what's in HEAD tonight. |
I've submitted the PR, and merged it's drone file and the main repositories. |
This is a thought I have had (as well as it has been mentioned in discord by others), but perhaps the docs repo should be merged into this repo.
Some pros of this:
I'd be open to making a PR for this, however my (simple) approach would be to create a docs folder, and just dump a copy of HEAD into it, this may lose history though.
The text was updated successfully, but these errors were encountered: