[Feature request] Uploading actual .git to visualize stuff

[artt]

One of the things that I found most useful about this is that I can test what would happen to my git repo if I do this and that. Sandboxing, you know.

For now, I have to work from the basic C0/C1 nodes and make it look more or less like the repo I'm working on. I was thinking it would be nice if the user could upload an actual .git (or whatever files need just to reproduce the graph... I'm a noob) to bypass this step.

To push this even further, I see lots of threads on stack overflow asking about git and people had to describe their setup in words. This project can be made into something similar to jsfiddle or codesandbox, but git sandbox instead. With this, they could link to the "sandbox" in their questions and people can just come and see.

The second point is kinda far off, since you would need a backend to store all this, but just an idea 😁

[artt]

To this end, I think factoring out this very well put together core logic modules into a separate library that people can build their own frontends/use cases (like one for lesson, another for sandboxing) would be really neat :)

[pcottle]

Thanks for the feedback!

To push this even further, I see lots of threads on stack overflow asking about git and people had to describe their setup in words. This project can be made into something similar to jsfiddle or codesandbox, but git sandbox instead. With this, they could link to the "sandbox" in their questions and people can just come and see.

There's actually something similar to this already; you can link into a specific gist id that represents a level or sandbox state:
https://learngitbranching.js.org/?gist_level_id=a84407351f9c9f0cb241

I think the remaining work to match something like jsfiddle would be to drive awareness of the feature, and help folks easily copy the data into a gist and create the permalink.

[artt]

Learning new things every day!

[artt]

Sorry. Didn't realize that the gist thing doesn't cover the first part.

[kaushalgautam]

Thanks for the feedback!

To push this even further, I see lots of threads on stack overflow asking about git and people had to describe their setup in words. This project can be made into something similar to jsfiddle or codesandbox, but git sandbox instead. With this, they could link to the "sandbox" in their questions and people can just come and see.

There's actually something similar to this already; you can link into a specific gist id that represents a level or sandbox state: https://learngitbranching.js.org/?gist_level_id=a84407351f9c9f0cb241

I think the remaining work to match something like jsfiddle would be to drive awareness of the feature, and help folks easily copy the data into a gist and create the permalink.

@pcottle - could you please explain the process? I am a little lost here :/

[pcottle]

Yeah sure, its a bit obscure like I mentioned. you can start with the build level instructions here:
https://github.com/pcottle/learnGitBranching#level-builder

once you finish that process, you will get a dialog that shows you a big JSON blob representing your level. copy that into a new github gist like so:
https://gist.github.com/pcottle/36ba1333c6b3639c0babaaffc351e1c9

then if you edit the permalink to point to that gist ID:
https://learngitbranching.js.org/?gist_level_id=36ba1333c6b3639c0babaaffc351e1c9

we will load up the gist and import that level automatically

[kaushalgautam]

Aaah, I see now. So the step of building the source tree to replicate your repo is still manual, but once replicated, we can share it easily using gist, right?

[pcottle]

Aaah, I see now. So the step of building the source tree to replicate your repo is still manual, but once replicated, we can share it easily using gist, right?

yep! Fwiw this is how I made all the levels myself; I found it far easier to use a GUI editor than typing out all the JSON manually