[PR #381] [MERGED] Fixing Startup Error (start_bambuddy.bat) #1018

Closed
opened 2026-05-06 12:34:30 +02:00 by BreizhHardware · 0 comments

📋 Pull Request Information

Original PR: https://github.com/maziggy/bambuddy/pull/381
Author: @nmori
Created: 2/15/2026
Status: Merged
Merged: 2/15/2026
Merged by: @maziggy

Base: 0.2.0bHead: fix/faile-to-start


📝 Commits (5)

  • 2bbe7b9 Bump markdown-it
  • 40f6ddc Merge pull request #363 from maziggy/dependabot/npm_and_yarn/frontend/npm_and_yarn-d1b1a1bb7d
  • 3ce9889 The script stopped launching after moving the folder, so I fixed it.
  • bb88527 Changed to use %~dp (for improved security)
  • fac02ff Merge branch '0.2.0b' into fix/faile-to-start

📊 Changes

2 files changed (+11 additions, -1 deletions)

View changed files

📝 frontend/package-lock.json (+1 -0)
📝 install/start_bambuddy.bat (+10 -1)

📄 Description

Description

  • The layout fix in Commit 8b3ea06 caused a discrepancy between the folder structure and what the script expects. This change addresses that layout fix.

Change Type

  • Bug fix (Incompatible change: Fixes an issue)
  • [] New feature (Incompatible change: Adds functionality)
  • Compatibility change (Modifies existing behavior or adds functionality)
  • Documentation update
  • Code refactoring
  • Performance improvement
  • Addition or update of tests

Implementation Details

  • When executing the script, if the script is located in the install folder, set the launch target folder to the folder one level above.

Testing

  • I have tested this on my local machine

Checklist

  • My code follows the project's coding style
  • I have commented my code where necessary
  • I have updated the documentation (if needed)
  • My changes generate no new warnings
  • I have tested my changes thoroughly

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/maziggy/bambuddy/pull/381 **Author:** [@nmori](https://github.com/nmori) **Created:** 2/15/2026 **Status:** ✅ Merged **Merged:** 2/15/2026 **Merged by:** [@maziggy](https://github.com/maziggy) **Base:** `0.2.0b` ← **Head:** `fix/faile-to-start` --- ### 📝 Commits (5) - [`2bbe7b9`](https://github.com/maziggy/bambuddy/commit/2bbe7b9da2d3d41b363c3e6b38c797c5603b6513) Bump markdown-it - [`40f6ddc`](https://github.com/maziggy/bambuddy/commit/40f6ddc059ac3875056f03af384ec9819e8cbec3) Merge pull request #363 from maziggy/dependabot/npm_and_yarn/frontend/npm_and_yarn-d1b1a1bb7d - [`3ce9889`](https://github.com/maziggy/bambuddy/commit/3ce98899fbdf7f78066697eddd1b41a5a81e4e6d) The script stopped launching after moving the folder, so I fixed it. - [`bb88527`](https://github.com/maziggy/bambuddy/commit/bb8852791515fa15f59f37dd6ebd78837e208c76) Changed to use %~dp (for improved security) - [`fac02ff`](https://github.com/maziggy/bambuddy/commit/fac02ff7b3e0eebb9a26d857290a3e15756e1d35) Merge branch '0.2.0b' into fix/faile-to-start ### 📊 Changes **2 files changed** (+11 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `frontend/package-lock.json` (+1 -0) 📝 `install/start_bambuddy.bat` (+10 -1) </details> ### 📄 Description ## Description - The layout fix in Commit 8b3ea06 caused a discrepancy between the folder structure and what the script expects. This change addresses that layout fix. ## Change Type - [X] Bug fix (Incompatible change: Fixes an issue) - [] New feature (Incompatible change: Adds functionality) - [ ] Compatibility change (Modifies existing behavior or adds functionality) - [ ] Documentation update - [ ] Code refactoring - [ ] Performance improvement - [ ] Addition or update of tests ## Implementation Details - When executing the script, if the script is located in the install folder, set the launch target folder to the folder one level above. ## Testing - [X] I have tested this on my local machine ## Checklist - [X] My code follows the project's coding style - [X] I have commented my code where necessary - [X] I have updated the documentation (if needed) - [X] My changes generate no new warnings - [X] I have tested my changes thoroughly --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
BreizhHardware 2026-05-06 12:34:30 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#1018
No description provided.