Conversation
|
|
|
|
✅ Deploy Preview for stackblitz-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
kirjavascript
left a comment
kirjavascript
left a comment
There was a problem hiding this comment.
Did a few passes, and this reads really well.
Feel free to ignore the comments and merge, they're either pedantic or unimportant.
|
|
||
| # {{ $frontmatter.title }} | ||
|
|
||
| The StackBlitz editor has some differences with respect to _persistence_ (whether and how we store your changes) between _projects_ and Git repositories. |
There was a problem hiding this comment.
Seems inconsistent to italicise projects, but not Git repositories
|
|
||
| In its default mode, the StackBlitz editor **does _not_ store your changes** when you open a Git repository (for instance, https://stackblitz.com/~/github.com/vitejs/vite). You can edit files, create new commits and push them to a remote. However, any intermediate changes that are not pushed will be lost after reloading the page. The editor shows a prominent warning to remind you when persistence is off. | ||
|
|
||
| This is in constrast with _projects_, which always keep your changes stored in the StackBlitz backend. The rough rationale for this difference in behavior is that, for Git-based projects, the ultimate goal is to push some new changes into a remote that already exists. This remote ultimately acts as your storage. |
There was a problem hiding this comment.
repeated use of ultimate. either one could be dropped and the sentence would still work
| * You should be logged in, and | ||
| * You should have push permissions for the repository, and | ||
| * You should not be working on the default branch. |
There was a problem hiding this comment.
, and feels superfluous in a list like this
| * Discard your old changes and start working fresh again from the latest commit. | ||
| * Push your ongoing changes to an intermediate branch and create a pull request. |
There was a problem hiding this comment.
if the convention from the previous list was followed, should the first item here end with , or?
I suppose the previous , and helps disambiguate here
2 participants
Summary of changes
Docs for the new git persistence mode.