@abhijitnathwani @paketb0te I think one thing we need to prioritize is adding in more subcommands so that Git-Sim covers at least all the basic Git subcommands.

Currently, git-sim supports the following 13 subcommands: log, status, add, restore, commit, stash, branch, tag, reset, revert, merge, rebase, cherry-pick

And even for these 13, there are some features not implemented yet, notably a wider set of ways to use Git rebase, which currently only allows 1 basic form of the command and no options for flexible rebases Git can do. Also, we don't have any detection so far for things like merge conflicts when merging. There also might be edge cases that are basically bugs right now or have confusing behavior, like resetting or reverting on a commit that isn't on the active branch.

Anyway, I think we should try to make a roadmap of Git subcommands that we'd like to implement. Here are some of my suggestions in order of priority:

• git checkout (in progress)
• git switch (in progress)
• git rm
• git mv
• git clean
• git fetch
• git pull
• git push
• git clone
• git reflog
• git diff
• git config
• git submodule
• git show
• git bisect
• git blame

I'm already working on the "git checkout" command which I can repurpose for "git switch" as well.

For the networking commands like fetch/push/pull I got a good suggestion in a comment on my original release, that we could clone the local repo to a dummy copy and perform the networked operation there. That would enable Git-Sim to get information about the operation and objects involved without directly impacting the local repo that the user is working in.

Let me know if either of you are interested in working on any specific subcommands or if you have suggestions for other subcommands to implement 😸