Right now it takes less (active) time from me to let Codex build a full feature in a Worktree, than it takes to open the project in Xcode, build and run it to test the result.
-
Right now it takes less (active) time from me to let Codex build a full feature in a Worktree, than it takes to open the project in Xcode, build and run it to test the result.
I‘m surely missing some obvious tools to streamline that process, any suggestions?
-
R relay@relay.infosec.exchange shared this topic
-
Right now it takes less (active) time from me to let Codex build a full feature in a Worktree, than it takes to open the project in Xcode, build and run it to test the result.
I‘m surely missing some obvious tools to streamline that process, any suggestions?
@myell0w I have not opened Xcode—literally—since November. No major extra third-party tools involved, just some vibecoded scripts and autowt for easy worktree management.
https://irskep.github.io/autowt/
This article covers all of the main points, and Codex can set most of it up for you.
My serup looks something like:
- Makefiles that expose all necessary operations (eg make run/app, make test/package PACKAGE=Messaging)
- Dedicated Simulator & DerivedData per worktree. -
@myell0w I have not opened Xcode—literally—since November. No major extra third-party tools involved, just some vibecoded scripts and autowt for easy worktree management.
https://irskep.github.io/autowt/
This article covers all of the main points, and Codex can set most of it up for you.
My serup looks something like:
- Makefiles that expose all necessary operations (eg make run/app, make test/package PACKAGE=Messaging)
- Dedicated Simulator & DerivedData per worktree.this sounds perfect, thank you!!
-
R relay@relay.publicsquare.global shared this topicR relay@relay.mycrowd.ca shared this topic
