langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Revision history Issue #21730

New Issue
Open
opened 2026-02-21 20:14:03 -05:00 by yindo · 7 comments
yindo commented 2026-02-21 20:14:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @fangoner on GitHub (Jan 18, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

v1.11.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When look back old revision in "Revision History", the current version is automatically recovered to the old version I was looking and lost major changes since lase issued version.

✔️ Expected Behavior

Please fix this problem asap. Really confuse me.

❌ Actual Behavior

No response

Originally created by @fangoner on GitHub (Jan 18, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version v1.11.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When look back old revision in "Revision History", the current version is automatically recovered to the old version I was looking and lost major changes since lase issued version. ### ✔️ Expected Behavior Please fix this problem asap. Really confuse me. ### ❌ Actual Behavior _No response_
yindo added the 🐞 bugstale labels 2026-02-21 20:14:03 -05:00
yindo commented 2026-02-21 20:14:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 18, 2026):

This bug is confirmed and has been fixed in newer versions of Dify. In v1.11.4, clicking an old revision in "Revision History" would immediately overwrite your current version, causing loss of unsaved changes. This was due to the frontend restoring the selected version without explicit confirmation or distinguishing between drafts and published versions.

A fix was merged after v1.11.4 (PR #30296), which ensures that selecting a draft restores your in-memory backup draft, and selecting a published version restores the published workflow—preventing accidental data loss. Another related update (PR #30300) improved version control and recovery by synchronizing version data in sessionStorage.

To resolve this, upgrade to a version that includes these fixes. Let me know if you need more details or upgrade instructions.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 18, 2026): <!-- Answer --> This bug is confirmed and has been fixed in newer versions of Dify. In v1.11.4, clicking an old revision in "Revision History" would immediately overwrite your current version, causing loss of unsaved changes. This was due to the frontend restoring the selected version without explicit confirmation or distinguishing between drafts and published versions. A fix was merged after v1.11.4 ([PR #30296](https://github.com/langgenius/dify/pull/30296)), which ensures that selecting a draft restores your in-memory backup draft, and selecting a published version restores the published workflow—preventing accidental data loss. Another related update ([PR #30300](https://github.com/langgenius/dify/pull/30300)) improved version control and recovery by synchronizing version data in sessionStorage. To resolve this, upgrade to a version that includes these fixes. Let me know if you need more details or upgrade instructions. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/65be679d-dbf6-4820-b347-87a1aaa27198?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/65be679d-dbf6-4820-b347-87a1aaa27198?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/65be679d-dbf6-4820-b347-87a1aaa27198?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/65be679d-dbf6-4820-b347-87a1aaa27198?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/65be679d-dbf6-4820-b347-87a1aaa27198?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/65be679d-dbf6-4820-b347-87a1aaa27198?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/65be679d-dbf6-4820-b347-87a1aaa27198?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20bug%20is%20confirmed%20and%20has%20been%20fixed%20in%20newer%20versions%20of%20Dify.%20In%20v1.11.4%2C%20clicking%20an%20old%20revision%20in%20%22Revision%20History%22%20would%20immediately%20overwrite%20your%20current%20version%2C%20causing%20loss%20of%20unsaved%20changes.%20This%20was%20due%20to%20the%20frontend%20restoring%20the%20selected%20version%20without%20explicit%20confirmation%20or%20distinguishing%20between%20drafts%20and%20published%20versions.%0A%0AA%20fix%20was%20merged%20after%20v1.11.4%20%28%5BPR%20%2330296%5D%28https%3A//github.com/langgenius/dify/pull/30296%29%29%2C%20which%20ensures%20that%20selecting%20a%20draft%20restores%20your%20in-memory%20backup%20draft%2C%20and%20selecting%20a%20published%20version%20restores%20the%20published%20workflow%E2%80%94preventing%20accidental%20data%20loss.%20Another%20related%20update%20%28%5BPR%20%2330300%5D%28https%3A//github.com/langgenius/dify/pull/30300%29%29%20improved%20version%20control%20and%20recovery%20by%20synchronizing%20version%20data%20in%20sessionStorage.%0A%0ATo%20resolve%20this%2C%20upgrade%20to%20a%20version%20that%20includes%20these%20fixes.%20Let%20me%20know%20if%20you%20need%20more%20details%20or%20upgrade%20instructions.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31168)
yindo commented 2026-02-21 20:14:04 -05:00
Author
Owner
Copy Link
Copy Source

@fangoner commented on GitHub (Jan 18, 2026):

I just updated to 1.11.4 yesterday, and come acroos this proble today. So you mean the 1.11.4 has been revised and I can update it again to fix this problem? Please confirm and thanks for quick reply.

@fangoner commented on GitHub (Jan 18, 2026): I just updated to 1.11.4 yesterday, and come acroos this proble today. So you mean the 1.11.4 has been revised and I can update it again to fix this problem? Please confirm and thanks for quick reply.
yindo commented 2026-02-21 20:14:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 18, 2026):

No, updating to v1.11.4 again will not fix the Revision History problem—v1.11.4 does not include the bug fix. The fix was merged after v1.11.4, so you’ll need to upgrade to a newer version released after 2025-12-30 to resolve this issue. There’s no workaround for v1.11.4; upgrading is the only confirmed solution. If you need help with upgrade steps, let me know! Details on the fix here.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 18, 2026): <!-- Answer --> No, updating to v1.11.4 again will not fix the Revision History problem—v1.11.4 does not include the bug fix. The fix was merged after v1.11.4, so you’ll need to upgrade to a newer version released after 2025-12-30 to resolve this issue. There’s no workaround for v1.11.4; upgrading is the only confirmed solution. If you need help with upgrade steps, let me know! [Details on the fix here](https://github.com/langgenius/dify/pull/30296). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/07a03d49-fd72-49d7-bfa8-4f35579987a0?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/07a03d49-fd72-49d7-bfa8-4f35579987a0?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/07a03d49-fd72-49d7-bfa8-4f35579987a0?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/07a03d49-fd72-49d7-bfa8-4f35579987a0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/07a03d49-fd72-49d7-bfa8-4f35579987a0?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/07a03d49-fd72-49d7-bfa8-4f35579987a0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/07a03d49-fd72-49d7-bfa8-4f35579987a0?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=No%2C%20updating%20to%20v1.11.4%20again%20will%20not%20fix%20the%20Revision%20History%20problem%E2%80%94v1.11.4%20does%20not%20include%20the%20bug%20fix.%20The%20fix%20was%20merged%20after%20v1.11.4%2C%20so%20you%E2%80%99ll%20need%20to%20upgrade%20to%20a%20newer%20version%20released%20after%202025-12-30%20to%20resolve%20this%20issue.%20There%E2%80%99s%20no%20workaround%20for%20v1.11.4%3B%20upgrading%20is%20the%20only%20confirmed%20solution.%20If%20you%20need%20help%20with%20upgrade%20steps%2C%20let%20me%20know%21%20%5BDetails%20on%20the%20fix%20here%5D%28https%3A//github.com/langgenius/dify/pull/30296%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31168)
yindo commented 2026-02-21 20:14:04 -05:00
Author
Owner
Copy Link
Copy Source

@fangoner commented on GitHub (Jan 18, 2026):

please let me know how to upgrade to fix this problem step by step. Thanks

@fangoner commented on GitHub (Jan 18, 2026): please let me know how to upgrade to fix this problem step by step. Thanks
yindo commented 2026-02-21 20:14:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 18, 2026):

To upgrade your self-hosted Dify (Docker) deployment and fix the Revision History bug, follow these steps:

  1. Back up your data: Save your database, Docker volumes, .env, and docker-compose.yaml files.
  2. Stop running containers: 
    docker compose down
  3. Update configuration files:
    Pull the latest code and update your docker-compose.yaml and .env files to match the new version. Compare with the latest .env.example and docker-compose.yaml from the repo. Migrate any custom settings.
  4. Pull the latest Docker images: 
    docker compose pull
  5. Start the updated containers: 
    docker compose up -d
  6. Run database and plugin migrations (inside the API container): 
    docker compose exec api uv run flask db upgrade
docker compose exec api uv run flask extract-plugins --workers=20
docker compose exec api uv run flask install-plugins --workers=2
docker compose exec api uv run flask migrate-data-for-plugin
  7. Adjust permissions if needed:
    For example, 
    sudo chown -R 1001:1001 ./volumes/app/storage
  8. Restart all services: 
    docker compose down && docker compose up -d
  9. Verify: Log in and check that everything works as expected.

There is no auto-upgrade script; the process is manual. Your data volumes can be reused as long as they are correctly mounted and preserved. Make sure to migrate any custom settings from your old configuration files to the new ones. If you have custom plugins or external databases, update their settings as well.
Reference: upgrade instructions

If you want the absolute latest fixes (including the Revision History bug fix merged after v1.11.4), make sure to upgrade to a version released after 2025-12-30. If you need help identifying the latest stable version, let me know!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 18, 2026): <!-- Answer --> To upgrade your self-hosted Dify (Docker) deployment and fix the Revision History bug, follow these steps: 1. **Back up your data**: Save your database, Docker volumes, `.env`, and `docker-compose.yaml` files. 2. **Stop running containers**: ``` docker compose down ``` 3. **Update configuration files**: Pull the latest code and update your `docker-compose.yaml` and `.env` files to match the new version. Compare with the latest `.env.example` and `docker-compose.yaml` from the repo. Migrate any custom settings. 4. **Pull the latest Docker images**: ``` docker compose pull ``` 5. **Start the updated containers**: ``` docker compose up -d ``` 6. **Run database and plugin migrations** (inside the API container): ``` docker compose exec api uv run flask db upgrade docker compose exec api uv run flask extract-plugins --workers=20 docker compose exec api uv run flask install-plugins --workers=2 docker compose exec api uv run flask migrate-data-for-plugin ``` 7. **Adjust permissions if needed**: For example, ``` sudo chown -R 1001:1001 ./volumes/app/storage ``` 8. **Restart all services**: ``` docker compose down && docker compose up -d ``` 9. **Verify**: Log in and check that everything works as expected. There is no auto-upgrade script; the process is manual. Your data volumes can be reused as long as they are correctly mounted and preserved. Make sure to migrate any custom settings from your old configuration files to the new ones. If you have custom plugins or external databases, update their settings as well. [Reference: upgrade instructions](https://github.com/langgenius/dify/issues/30214#issuecomment-3692661835) If you want the absolute latest fixes (including the Revision History bug fix merged after v1.11.4), make sure to upgrade to a version released after 2025-12-30. If you need help identifying the latest stable version, let me know! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/8f84db0e-ef63-4526-ab12-316a0d9666ed?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8f84db0e-ef63-4526-ab12-316a0d9666ed?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8f84db0e-ef63-4526-ab12-316a0d9666ed?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8f84db0e-ef63-4526-ab12-316a0d9666ed?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8f84db0e-ef63-4526-ab12-316a0d9666ed?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8f84db0e-ef63-4526-ab12-316a0d9666ed?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8f84db0e-ef63-4526-ab12-316a0d9666ed?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=To%20upgrade%20your%20self-hosted%20Dify%20%28Docker%29%20deployment%20and%20fix%20the%20Revision%20History%20bug%2C%20follow%20these%20steps%3A%0A%0A1.%20%2A%2ABack%20up%20your%20data%2A%2A%3A%20Save%20your%20database%2C%20Docker%20volumes%2C%20%60.env%60%2C%20and%20%60docker-compose.yaml%60%20files.%0A2.%20%2A%2AStop%20running%20containers%2A%2A%3A%20%20%0A%20%20%20%60%60%60%0A%20%20%20docker%20compose%20down%0A%20%20%20%60%60%60%0A3.%20%2A%2AUpdate%20configuration%20files%2A%2A%3A%20%20%0A%20%20%20Pull%20the%20latest%20code%20and%20update%20your%20%60docker-compose.yaml%60%20and%20%60.env%60%20files%20to%20match%20the%20new%20version.%20Compare%20with%20the%20latest%20%60.env.example%60%20and%20%60docker-compose.yaml%60%20from%20the%20repo.%20Migrate%20any%20custom%20settings.%0A4.%20%2A%2APull%20the%20latest%20Docker%20images%2A%2A%3A%20%20%0A%20%20%20%60%60%60%0A%20%20%20docker%20compose%20pull%0A%20%20%20%60%60%60%0A5.%20%2A%2AStart%20the%20updated%20containers%2A%2A%3A%20%20%0A%20%20%20%60%60%60%0A%20%20%20docker%20compose%20up%20-d%0A%20%20%20%60%60%60%0A6.%20%2A%2ARun%20database%20and%20plugin%20migrations%2A%2A%20%28inside%20the%20API%20container%29%3A%20%20%0A%20%20%20%60%60%60%0A%20%20%20docker%20compose%20exec%20api%20uv%20run%20flask%20db%20upgrade%0A%20%20%20docker%20compose%20exec%20api%20uv%20run%20flask%20extract-plugins%20--workers%3D20%0A%20%20%20docker%20compose%20exec%20api%20uv%20run%20flask%20install-plugins%20--workers%3D2%0A%20%20%20docker%20compose%20exec%20api%20uv%20run%20flask%20migrate-data-for-plugin%0A%20%20%20%60%60%60%0A7.%20%2A%2AAdjust%20permissions%20if%20needed%2A%2A%3A%20%20%0A%20%20%20For%20example%2C%20%20%0A%20%20%20%60%60%60%0A%20%20%20sudo%20chown%20-R%201001%3A1001%20./volumes/app/storage%0A%20%20%20%60%60%60%0A8.%20%2A%2ARestart%20all%20services%2A%2A%3A%20%20%0A%20%20%20%60%60%60%0A%20%20%20docker%20compose%20down%20%26%26%20docker%20compose%20up%20-d%0A%20%20%20%60%60%60%0A9.%20%2A%2AVerify%2A%2A%3A%20Log%20in%20and%20check%20that%20everything%20works%20as%20expected.%0A%0AThere%20is%20no%20auto-upgrade%20script%3B%20the%20process%20is%20manual.%20Your%20data%20volumes%20can%20be%20reused%20as%20long%20as%20they%20are%20correctly%20mounted%20and%20preserved.%20Make%20sure%20to%20migrate%20any%20custom%20settings%20from%20your%20old%20configuration%20files%20to%20the%20new%20ones.%20If%20you%20have%20custom%20plugins%20or%20external%20databases%2C%20update%20their%20settings%20as%20well.%20%20%0A%5BReference%3A%20upgrade%20instructions%5D%28https%3A//github.com/langgenius/dify/issues/30214%23issuecomment-3692661835%29%0A%0AIf%20you%20want%20the%20absolute%20latest%20fixes%20%28including%20the%20Revision%20History%20bug%20fix%20merged%20after%20v1.11.4%29%2C%20make%20sure%20to%20upgrade%20to%20a%20version%20released%20after%202025-12-30.%20If%20you%20need%20help%20identifying%20the%20latest%20stable%20version%2C%20let%20me%20know%21)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/31168)
yindo commented 2026-02-21 20:14:04 -05:00
Author
Owner
Copy Link
Copy Source

@fangoner commented on GitHub (Jan 18, 2026):

Does not work

@fangoner commented on GitHub (Jan 18, 2026): Does not work
yindo commented 2026-02-21 20:14:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 18, 2026):

Hi, @fangoner. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that in Dify v1.11.4 (self-hosted via Docker), viewing an old revision in "Revision History" reverts the current version, causing loss of recent changes.
  • This bug was confirmed and fixed after v1.11.4 with PR #30296 and #30300, requiring an upgrade to a version released after 2025-12-30.
  • Detailed manual upgrade instructions were provided to resolve the issue.
  • You later commented that the fix "Does not work," suggesting the problem may persist or the upgrade was unsuccessful.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify; if so, you can keep the discussion open by commenting here.
  • Otherwise, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 18, 2026): Hi, @fangoner. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that in Dify v1.11.4 (self-hosted via Docker), viewing an old revision in "Revision History" reverts the current version, causing loss of recent changes. - This bug was confirmed and fixed after v1.11.4 with PR #30296 and #30300, requiring an upgrade to a version released after 2025-12-30. - Detailed manual upgrade instructions were provided to resolve the issue. - You later commented that the fix "Does not work," suggesting the problem may persist or the upgrade was unsuccessful. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify; if so, you can keep the discussion open by commenting here. - Otherwise, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label stale 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21730
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?