Skip to content
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

Provide some minimal git integration #489

Closed
callegar opened this issue May 4, 2023 · 7 comments
Closed

Provide some minimal git integration #489

callegar opened this issue May 4, 2023 · 7 comments

Comments

@callegar
Copy link

callegar commented May 4, 2023

Did you check if a similar feature request has already been reported?

Checked, not reported

Is your feature request related to a problem? Please describe.

Keeping old versions of the tasks (in case some task is accidentally deleted), easing synchronization of tasks among multiple computers.

Describe the solution you'd like

todo.txt files are line based text files. This is the ideal format for taking diffs and for storing in a revision control system, such as git. Would be great to have some form of git integration modeled after what is offered in the pass password manager (https://www.passwordstore.org/) and its QtPass frontend (https://github.com/IJHack/QtPass).

This would work as follows:

  1. When sleek realizes that a configured todo file is in a directory under git control (i.e., with a .git subdir) and that git is available, activate git integration
  2. When git integration is active if a todo file in a directory under revision control is modified, perform a commit in that dir. Alternatively, provide a commit button for the user to manually commit the file being worked upon to git
  3. Provide a pull and a push button, resulting in git pull and git push.
@mimmori
Copy link

mimmori commented May 5, 2023

+1

@warmwaffles
Copy link

Currently the work around I have been doing is manual. I just go to the directory, git add . and then commit the changes. This would reduce my need to remember to do that.

@ransome1 ransome1 added this to Up for discussion in sleek v1.x May 15, 2023
@github-actions github-actions bot added the Stale label Jul 19, 2023
Repository owner deleted a comment from github-actions bot Jul 20, 2023
@ransome1 ransome1 removed the Stale label Jul 20, 2023
@github-actions
Copy link

This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now.

@callegar
Copy link
Author

Unclear to me whether this will automatically be closed also in the sleek 2.x backlog. Please, keep it open there.

@ransome1
Copy link
Owner

Your comment should be enough to keep it open.

@andrei-a-papou
Copy link

andrei-a-papou commented Dec 15, 2023

At least for Unix-like systems, an easy solution is to use https://github.com/gitwatch/gitwatch. Haven't tested, but it should also work with Cygwin/WSL/Git Bash/etc.

This script https://bitbucket.org/brendanp/git-prime/src/master/ is reported to work under Cygwin.

And if one uses Syncthing, it can be quickly configured to keep a bunch of backups (might be enough in many cases -- and this is what I'm using right now.)

Copy link

This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
sleek v1.x
Up for discussion
Development

No branches or pull requests

5 participants