You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/testing-deployment-publishing/branching-collaboration/branching.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Branching creates a separate copy of your work, so you can add new features with
14
14
Suppose you have an eCommerce app and you want to add a new feature, such as a product recommendation system. Instead of incorporating it directly into your `main` branch and potentially causing problems, you can create a branch to work on this new feature in isolation. Once it's complete, you can integrate it back into the `main` branch.
15
15
16
16
:::info
17
-
This feature is only available for Pro, Teams and Enterprise users.
17
+
While all users can access the branching menu and create commits, only **Pro**, **Teams**, and **Enterprise** plans support creating new branches.
@@ -13,40 +13,10 @@ In this section, we discuss the important concepts of saving and versioning in y
13
13
14
14
## Versions
15
15
16
-
Versions enable you to save specific named states of your project. This function is particularly useful for recovery purposes. If you accidentally delete a page or component or change settings, you can easily revert to a saved version.
17
-
18
-
### Saving a version
19
-
20
-
Saving the latest changes will store the current state of your app in the version control. In the future, if anything goes wrong, you can restore your app to the currently saved state.
21
-
22
-
Ideally, you should save the version whenever you accomplish something important, for example, after finishing a page, adding configuration, etc.
23
-
24
-
<div style={{
25
-
position: 'relative',
26
-
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
You can no longer create new versions in FlutterFlow. However, any previously created versions will remain accessible. Moving forward, we recommend using [**Commits**](#commits), which provides a more robust way to track changes and manage your project history.
0 commit comments