github-starred/yaak
2
0
Fork 0
mirror of https://github.com/mountain-loop/yaak.git synced 2026-05-06 18:16:03 -05:00
Code Issues 71 Packages Projects Releases 101 Wiki Activity

[PR #396] [MERGED] Support moving multiple requests to another workspace #946

New Issue
Closed
opened 2026-04-20 19:53:26 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 19:53:26 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/mountain-loop/yaak/pull/396
Author: @pathikb
Created: 2/14/2026
Status: ✅ Merged
Merged: 2/16/2026
Merged by: @gschier

Base: main ← Head: feature/bulk-move-requests

📝 Commits (3)

  • 2998331 Add bulk move feature for moving multiple requests to another workspace
  • d7f40e0 Consolidate bulk move into existing MoveToWorkspaceDialog
  • e37f616 Add sidebar.selected.move hotkey action with empty default binding

📊 Changes

4 files changed (+59 additions, -26 deletions)

View changed files

📝 src-web/commands/moveToWorkspace.tsx (+10 -3)
📝 src-web/components/MoveToWorkspaceDialog.tsx (+23 -15)
📝 src-web/components/Sidebar.tsx (+22 -8)
📝 src-web/hooks/useHotKey.ts (+4 -0)

📄 Description

CleanShot 2026-02-16 at 06 16 08
  • Create BulkMoveToWorkspaceDialog component for selecting target workspace
  • Create bulkMoveToWorkspace command for handling bulk move operations
  • Add 'Move N Requests' context menu item in Sidebar for multi-selection
  • Clear folderId when moving since folders don't exist across workspaces
  • Show toast notification with option to switch to target workspace

🔄 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/mountain-loop/yaak/pull/396 **Author:** [@pathikb](https://github.com/pathikb) **Created:** 2/14/2026 **Status:** ✅ Merged **Merged:** 2/16/2026 **Merged by:** [@gschier](https://github.com/gschier) **Base:** `main` ← **Head:** `feature/bulk-move-requests` --- ### 📝 Commits (3) - [`2998331`](https://github.com/mountain-loop/yaak/commit/2998331592cab4d84263dea5a866769c9eb7bbf3) Add bulk move feature for moving multiple requests to another workspace - [`d7f40e0`](https://github.com/mountain-loop/yaak/commit/d7f40e03ad3297ab4cb2411f094061719fa71f4d) Consolidate bulk move into existing MoveToWorkspaceDialog - [`e37f616`](https://github.com/mountain-loop/yaak/commit/e37f6160aecb4153aa7fb4a73ce61be9d2a6e183) Add sidebar.selected.move hotkey action with empty default binding ### 📊 Changes **4 files changed** (+59 additions, -26 deletions) <details> <summary>View changed files</summary> 📝 `src-web/commands/moveToWorkspace.tsx` (+10 -3) 📝 `src-web/components/MoveToWorkspaceDialog.tsx` (+23 -15) 📝 `src-web/components/Sidebar.tsx` (+22 -8) 📝 `src-web/hooks/useHotKey.ts` (+4 -0) </details> ### 📄 Description <img width="1032" height="540" alt="CleanShot 2026-02-16 at 06 16 08" src="https://github.com/user-attachments/assets/8ef6c2ea-733d-477f-9c99-1226a3a4ff9b" /> - Create BulkMoveToWorkspaceDialog component for selecting target workspace - Create bulkMoveToWorkspace command for handling bulk move operations - Add 'Move N Requests' context menu item in Sidebar for multi-selection - Clear folderId when moving since folders don't exist across workspaces - Show toast notification with option to switch to target workspace --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-20 19:53:26 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/yaak#946
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?