docs for new git persistence mode #222
Open
+56
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
|
✅ Deploy Preview for stackblitz-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
kirjavascript
approved these changes
Jun 27, 2024
|
|
||
| # {{ $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
Comment on lines
+21
to
+23
| * 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
Comment on lines
+49
to
+50
| * 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
Docs for the new git persistence mode.