Let the user decide if you want to create a git repository or not #7705
Replies: 1 comment
|
Hiring: Senior AI Video Automation Developer (Python + Remotion) We're hiring a full-time developer to build an AI-powered video generation system. The software takes a script + voiceover and automatically generates a fully edited video. Reference: Requirements: • Strong Python development experience DO NOT APPLY IF: • You have never built a complete software product Application Instructions (IMPORTANT): Applications that do not follow these instructions will be ignored automatically. Send me a DM containing ONLY:
In the Loom, cover ALL of the following: • Show your face briefly at the start
Text applications, resumes without Loom videos, AI-generated applications, and copy-pasted messages will not be reviewed. Budget: Position: Looking to hire immediately. |
Uh oh!
There was an error while loading. Please reload this page.
Hello and thank you very much for remotion. Video as code is what my nerdy developer child needs.
I think the script to initialize a new project has a weird limitation, which is that it doesn't create a new Git repository if you create the folder inside another repository. I understand that this is not common, but in my case I do this a lot.
The only option the CLI gives you is to continue without creating a Git repository or not continue. I don't understand that limitation. The question should be: do you want to create a nested Git repository or not? In my case, I actually want to do that, and with the current state of the tool I have to go into the directory and initialize the Git repository myself. It's not a big deal, but I don't understand the intention behind this.
All reactions