mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-23 17:52:49 +00:00
Christoph LeiterandClaude Opus 5
51a435d3cf
* feat(app): find workspaces by PR/MR number in the command center The command center matched workspaces on title, host, project, and branch. Typing the change-request number you actually remember found nothing, so you had to recall the branch name instead. Workspace results now carry their pull/merge request number, and a numeric query resolves it directly: 42, #42, !42, pr 42, and mr 42 all reach the same workspace. Matching compares the parsed number exactly rather than as a substring, so 42 no longer drags in PR 142 or a branch that happens to contain those digits. Exact number hits sort above ordinary text matches for the same query. Nothing changes visually. The number is a search key only; result rows render exactly as before. The number is read from the pull request the daemon already sends. selectPrHintFromStatus is the fallback only: it derives the number by parsing the PR/MR URL, which yields nothing for a noncanonical or absent URL even when the daemon sent a usable number. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * test(app): exercise change-request parsing through the matcher parseChangeRequestQuery was exported only so the test could reach it, which made an implementation helper part of the module surface and let the parser cases pass without covering how the parser composes with workspace matching. Unexport it and drive the same spellings through matchWorkspaceQuery. The rejection cases now assert what they actually protect: a query like fix-42-retries must not take the number path, so a workspace whose PR is 42 does not match it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Welcome to your Expo app 👋
This is an Expo project created with create-expo-app.
Get started
-
Install dependencies
npm install -
Start the app
npx expo start
In the output, you'll find options to open the app in a
- development build
- Android emulator
- iOS simulator
- Expo Go, a limited sandbox for trying out app development with Expo
You can start developing by editing the files inside the app directory. This project uses file-based routing.
Get a fresh project
When you're ready, run:
npm run reset-project
This command will move the starter code to the app-example directory and create a blank app directory where you can start developing.
Learn more
To learn more about developing your project with Expo, look at the following resources:
- Expo documentation: Learn fundamentals, or go into advanced topics with our guides.
- Learn Expo tutorial: Follow a step-by-step tutorial where you'll create a project that runs on Android, iOS, and the web.
Join the community
Join our community of developers creating universal apps.
- Expo on GitHub: View our open source platform and contribute.
- Discord community: Chat with Expo users and ask questions.
Dictation debugging
Set EXPO_PUBLIC_ENABLE_AUDIO_DEBUG=1 before running npx expo start to render the in-app audio debug card. Pair it with the server-side STT_DEBUG_AUDIO_DIR flag so every dictation includes a copyable path to the saved raw audio file.