Content Save Failure When Re-Using Deleted Branch Name

[samsmithssw]

Describe the issue that you're seeing. Any Loom videos or screenshots usually help a lot!

@amankumarrr
I made some content changes to a webpage and then when I saved the changes and created a new branch this error came up. All of my changes were lost.

Figure: First error message Figure: Second error message once first was closed

Reproduction

n/a

Steps to reproduce

1. Make changes
2. Save changes
3. Create a branch
4. Get it merged.
5. Make changes again
6. Save changes again
7. Create a branch with the same branch name.

System Info

n/a

Validations

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that reports the same bug.

[kldavis4]

@samsmithssw what error(s) are there in the browser console?

[samsmithssw]

@samsmithssw what error(s) are there in the browser console?

This is the error message in the console @kldavis4

**Figure: console error message**

[kldavis4]

thanks - so you are re-using the same branch name? Does it happen when you use a different branch name in step 7?

[amankumarrr]

@samsmithssw

Hey @kldavis4,

The issue arises when an old branch is deleted on GitHub, and an attempt is made to create a new branch with the same name in Tina. The editorial workflow permits the creation of such a branch since it's deleted on GitHub. However, upon indexing in the Tina Cloud, a conflict arises as the branch already exists there.

Potential solutions:

1. Implement a check before indexing in the Tina Cloud to prevent the creation of a branch with the same name.
2. Allow users to delete branches directly from the Tina Cloud.

[kldavis4]

There is a webhook that handles deletion of the branch in Tina Cloud when it is deleted from GitHub. It sounds like possibly there is a failure on the deletion.

[amankumarrr]

@kldavis4 is it something we need to fix it on our end?

[kldavis4]

Unclear at this point. Just needs to be investigated because under normal circumstances there shouldn't be a branch naming conflict