move all source files to a subfolder #151751
Replies: 2 comments 2 replies
-
|
@victimofleisure there must be another way, but it was easy to do it in the command line 🤷🏾, here is the Pull request victimofleisure/Whorld#1 , I hope I got it right and moved everything one level down, nice project by the way 👍🏾 |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi. I run a repo called Whorld. I would like to move all of the source files that are currently in trunk down a level, into a new subfolder called Whorld. It currently looks like this:
But it should look like this:
I would like to do this without bloating the repo by creating an extra copy of every single source file. That would be ugly!
I would also like to avoid using the command line, as I'm a Windows queen and don't want to mess with cryptic commands that I don't understand.
The GitHub instructions say I can do this in GitHub.dev which I tried. I'm able to create the subfolder, select all the source files, and drag and drop them all in the subfolder. Super. But when I try to commit the change, it loops for about 30 seconds while counting down and acting like it's making progress, but then it always fails with the uninformative message "Can't commit."
I usually use GitHub desktop for everything. So I could do this change in my local working copy, and commit it. That's easy, but I'm not sure it's the right thing to do. Is GitHub desktop smart enough to avoid adding a second copy of every source file to the repo?
Sorry if I'm asking a FAQ but I tried pretty hard to answer this by myself and even asked GPT but didn't get any workable answers.
Best
Chris
Beta Was this translation helpful? Give feedback.
All reactions