Modify ↓
#8803 closed enhancement (duplicate)
wiki within a revision-control system
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | wiki system | Version: | none |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I don't know if this has been considered before, but one thing I'd like to see is storage of the wiki within a repository. (This will probably work better when using multiple repositories is fully supported.)
There's two main advantages I can think of to this:
- allows use of the same history system as the code
- allows easy migration and syncing of data
- this potentially allows offline work on a wiki followed by a later merge
Just to let you know I appreciate trac, I've looked at other possibilities for a wiki-in-git, but don't like any other wiki's I've tried as much as trac's! (googlecode does put it's wiki in an svn branch, github doesn't really (yet), but they're repository view will format wiki files so it's sort-of doable (but in-browser editing doesn't work).)
Attachments (0)
Note:
See TracTickets
for help on using tickets.
Yes, this has been considered before: #1132, #1465 (for more than wiki pages, actually).