Multiple branches with the same name appearing on their own.

[charliefabley]

Has your issue been reported?

• I have searched the existing issues and confirm it has not been reported.
• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Both new and old branches have apparently replicated themselves with the same name. Some of them have different edit times, which is a bit disconcerting

Expected Behavior

That there was only one branch with one unique name, and that they should not replicate themselves.

Steps to Reproduce

Go to our project and look at the branches

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4KkvLlw4x2ruZE7rruK/lVtCYWNjsja7sslsJtbwAdNYvpG7l/S8+kfhNuXbC0dAhleWKKgmUK+vPemvHtEvE6CzqWRZxd1s1pEw/gWn+hbq67EajpYG5/De1YN3Ky1qSskSNAJsxhLnhg1ziHNd6RTgnDNr34DDEzAOaaOZOK2SrDX1iXc2URm05KZDPz

Context

We have we have had numerous problems with marge, that has left us losing hours if not sometimes days of work. This appears just to be another bug in the merged system.

Visual documentation

Additional Info

No additional information

Environment

- FlutterFlow version: 
- Platform: Windows current and web version
- Browser name and version: web version and chrome
- Operating system and version affected: windows 11 and 12

General

• I was collaborating with other users in the same project prior to data loss
• I navigated between different project views leading up to data loss
• The UI was running very slowly prior to data loss
• A crash or other bug occurred prior to data loss
• Data was not saved in a snapshot
• I was using flutterflow from multiple devices
• I was using flutterflow from multiple platforms (e.g. both web and MacOS Desktop app)

Relative to the time the changes were made, data was lost within

• 1 minute
• 1 hour
• 1 day
• 1 week

When following my steps to reproduce, data loss happens

• ~100% of the time
• ~50% of the time
• ~10% of the time
• ~1% of the time
• Very rarely or only encountered once

[ignalauret]

Hey @charliefabley thanks for your report. Could you describe me how did you do to get multiple branches? So which are the steps I should follow to replicate this? It would be really helpful for our technical team.

[charliefabley]

I'm not sure that we necessarily did anything, it just happened. It was a colleague of mine and she reported it to me fairly swiftly, and said that she had simply created a branch, and came back to me I believe within an hour of two of it happening. So all I can say is that we did nothing out of the ordinary. They remained there until today, when I suggested that she merged the one she'd been working on most recently, and deleted the others. The merge worked.

…

On Tue, May 7, 2024 at 3:06 PM Ignacio Lauret ***@***.***> wrote: Hey @charliefabley <https://github.com/charliefabley> thanks for your report. Could you describe me how did you do to get multiple branches? So which are the steps I should follow to replicate this? It would be really helpful for our technical team. — Reply to this email directly, view it on GitHub <#2866 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEUI4UO7MW5WZ2I5ZRBW5SDZBEQ43AVCNFSM6AAAAABHLFDE3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZGEYTQMZRHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[github-actions]

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.