kiprasmel / git-backup Goto Github PK

Task

Create a Makefile that would

• install the script in the appropriate /usr location - 7b2a6f0
  • re-search the proper /usr location
• Update README - 3021bef
• install & gzip the manual page (git-backup(1)) (why gzip?)

Notes

probably use install & gzip utils.

maaaaybe consider windows? lmao normies

High priority, since the user has to manually add the script to his path or the appropriate /usr location.

Same with the manual page. And the -m option won't work since the manual page is not provided.

Task

• Create a function which delete backups
  • Figure out how we want to display current backups so that we can
    • select one or multiple of them
  • One of them
  • Multiple
  • All
  • Make it work with remote backups (git push origin :branch-name)

{
	do_stuff
	doSomeMoreStuff
} || {
	check_for_error_1 && handle_error_1
	checkForError2 && handleError2
}

This will be useful in restoring the git stash, independent of either a failure or success.
This will probable require a finally thingie.
Or maybe consider wrapping the function up? Maybe?

I've been searching for a similar tool before creating it myself, and I think that it'd probably be useful to let future observers know about a (((working))) solution available.

• https://stackoverflow.com/questions/1550378/is-it-possible-to-push-a-git-stash-to-a-remote-repository

Task

Update README.md with

• description
• installation info (preferably, using Makefile with make - see #1)
• installation info for arch users (yay -S git-backup once #2 is done)

More testing needed. The manual will probly hold the answers.

Task

• Create a function which would restore changes from

  • XYZ backup

    • list backups - #6
      • select one to restore from

  • latest backup

    • Identify the latest backup (probably by the unix date timestamp we add to the branch name) (create as separate function since it'd be needed for other stuff too)

• implement an option to activate this function

  • think of a good name
  • handle in the script
  • update docs
    • raw
    • manual page

There's some bad sh1t happening if you run git-backup in an untracked directory.

I don't know if this also happens with just regular git stash -u (probably?)

I need to investigate more (I just wasted an hour+ trying to recover; I succeeded, but boy was this stressful).

What helped me recover was:

1. checking my shell history - when was the last time I ran git-backup
2. going through git reflog --all and finding a commit that has a date very similar to the one found in the shell's history. Mine was identical.
3. git stash apply <COMMIT-ISH>

Task

Create an AUR package because I use arch btw

• figure out how
  ...
• update documentation (see #3)

Edit:

For reference, just like with the Makefile, take a look at mutt-wizard's PKGBUILD.

Task

• Create a function which would list backups

  • Local backups
  • Remote backups
  • Both
  • Decide which backups should be listed by default

• Implement an option to activate this function

  • think of a good name
  • handle in the script
  • update docs
    • raw
    • manual page

• Make it extendable for other commands (see #4 & #5)

  • Make a single or multiple backups selectable (probably in interactive mode, something like git rebase -i)

Future

• Display which ones can be backed up (to where HEAD points to, checking if the changes could apply without conflicts (check by commits/refs/whatever-works, if possible, to avoid having to test every backup))