Austin Wise
Austin Wise
Support reading and writing files from a Git repository. This includes bare repos. Features include: * [x] #34 * [x] #35 * [x] #36 * [ ] Viewing file change...
It should be easy to search for content in the wiki. Even basic searching is useful, but there is a lot that can be done to make the experience great:...
The program should be easy to acquire. * [x] Automatic CI builds for every release * [x] #19 * [x] No internet connection should be required after the program is...
The wiki should be writable from the website. Features include: * [x] #16 * [x] #51 * [ ] Some amount syntax highlighting? * [ ] Maybe embed the VS...
Security is not a huge issue, as the current intended use case is a single person viewing data they wrote. However there are some things we should watch out for...
The latest release API [is documented](https://docs.github.com/en/rest/reference/releases#get-the-latest-release) to return the most recent release based on creation time. This means that if I make a patch for an old version, that will...
Presumably [`Tree.walk`](https://docs.rs/git2/latest/git2/struct.Tree.html#method.walk) would be faster than the current method, which traverses from the root to every directory.
It might be helpful for customer support purposes to have a Git hash and version number easily accessible on the web page. And also in the `--version` command for that...
There are two ways I can think of to do this: * Redirect back to the edit page with the modified content. Display an alert with the error message. *...