Proposal: Merge docs into this repo #1218

New Issue

GiteaMirror · 2025-11-02T03:52:46-06:00

GiteaMirror commented

2025-11-02 03:52:46 -06:00

Originally created by @techknowlogick on GitHub (Nov 6, 2017).

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:

When submitting PRs, devs can submit docs in same commit (this reduces friction for su
An extra step to drone can happen on merges that autobuild and push docs (to keep them fresh)

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.

Originally created by @techknowlogick on GitHub (Nov 6, 2017). 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: * When submitting PRs, devs can submit docs in same commit (this reduces friction for su * An extra step to drone can happen on merges that autobuild and push docs (to keep them fresh) 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.

GiteaMirror added the type/proposal type/docs labels 2025-11-02 03:52:46 -06:00

GiteaMirror closed this issue

2025-11-02 03:52:46 -06:00

GiteaMirror commented

2025-11-02 03:52:47 -06:00

@lafriks commented on GitHub (Nov 6, 2017):

docker yml also need to be updated so that docs site is updated from main repository

@lafriks commented on GitHub (Nov 6, 2017): docker yml also need to be updated so that docs site is updated from main repository

GiteaMirror commented

2025-11-02 03:52:47 -06:00

@andreynering commented on GitHub (Nov 7, 2017):

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.

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.

With Git Subtrees would be possible to merge the repos preserving the history.

@andreynering commented on GitHub (Nov 7, 2017): 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. > 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. With Git Subtrees would be possible to merge the repos preserving the history.

GiteaMirror commented

2025-11-02 03:52:47 -06:00

@lafriks commented on GitHub (Nov 7, 2017):

Idea for moving docs to main repo is to be able submit documentation together with updated code otherwise docs stay out of date

@lafriks commented on GitHub (Nov 7, 2017): Idea for moving docs to main repo is to be able submit documentation together with updated code otherwise docs stay out of date

GiteaMirror commented

2025-11-02 03:52:48 -06:00

@lunny commented on GitHub (Nov 7, 2017):

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 /docs .

@lunny commented on GitHub (Nov 7, 2017): 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 `/docs` .

GiteaMirror commented

2025-11-02 03:52:48 -06:00

@lafriks commented on GitHub (Nov 7, 2017):

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

@lafriks commented on GitHub (Nov 7, 2017): 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

GiteaMirror commented

2025-11-02 03:52:48 -06:00

@techknowlogick commented on GitHub (Nov 7, 2017):

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.

@techknowlogick commented on GitHub (Nov 7, 2017): 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.

GiteaMirror commented

2025-11-02 03:52:49 -06:00

@techknowlogick commented on GitHub (Nov 8, 2017):

I've submitted the PR, and merged it's drone file and the main repositories.

@techknowlogick commented on GitHub (Nov 8, 2017): I've submitted the PR, and merged it's drone file and the main repositories.

GiteaMirror referenced this issue

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

[PR #1218] [MERGED] fix #1189, commit messages containing a pipe #15817

Sign in to join this conversation.