2 ms·
At first I was excited about this. Then I tried it. There is no working set. Reloading the web page loses all changes. This would have been a nice path to brin
by abtinf 8y ago
At first I was excited about this. Then I tried it. There is no working set. Reloading the web page loses all changes.
This would have been a nice path to bring less technical folks into gitlab, say for writing articles and other copy. But I can already imagine the non-stop complaints about losing work.
- exikyut 8y agoWell, that shouldn't be very hard to solve; at the worst save the "working set" in a UI-specific cache (aka detached from the git repo), and maybe offer options for autosaving into branches. I do agree this is something that needs to be solved, but cannot categorically be solved elegantly, so GitLab needs to just get on with just doing what will work.