Software & DevOps

Move public creative sketches into a GitHub repo, one commit per project

The scene

You have many public sketches on a creative platform and want them archived in your own GitHub repository, with one folder and one commit per project, and a review before anything is pushed.

Tools involved

CodexReproducible in ChinaEvidence: Second-hand / directory record

What they did

  1. Confirm you have the right to move these public or owned projects, and prepare the destination repository.
  2. Grant only the GitHub access the job needs. Ask for one folder per project, a short README, and one commit per project.
  3. Before any push, have it show you the repo layout and a couple of sample commits, and check licences and third-party assets.
  4. Push only after you approve. If you want a gallery, ask for GitHub Pages as a separate step.

Copyable prompt

Please move my public projects from [profile or collection I own] into the GitHub repository [repo]. For each project, put the code and assets in their own folder, add a short README, and make one commit. Show me the repository layout and a sample commit before you push. Do not push until I approve.

Rewritten here for you to try; not a verbatim excerpt from elsewhere. What it asks:Fill in a source you own and the destination repo. It should commit per project and wait before pushing.

Things to watch

The public listing said 200+ sketches were archived in under 10 minutes and that GitHub Pages went up quickly. Those figures are second-hand, with no error rate, and were not retested here. Move only projects you have the right to handle, and check licences. Generally reproducible in China if you can use GitHub and a coding agent.

Codex or a similar coding agent, plus a GitHub repository.