d6e9b0a72b
Summary: We’ll use this to create the repositories on disk and then push them to GitHub. Test Plan: Generate both kinds of repository, and check out the SHAs: ```shell $ yarn backend $ node bin/createExampleRepo.js /tmp/repo $ node bin/createExampleRepo.js --submodule /tmp/repo-submodule $ node bin/createExampleRepo.js --no-submodule /tmp/repo-no-submodule $ # (first and third lines do the same thing) $ git -C /tmp/repo rev-parse HEAD 677b340674bde17fdaac3b5f5eef929139ef2a52 $ git -C /tmp/repo-submodule rev-parse HEAD 29ef158bc982733e2ba429fcf73e2f7562244188 $ git -C /tmp/repo-no-submodule rev-parse HEAD 677b340674bde17fdaac3b5f5eef929139ef2a52 ``` Then, note that these SHAs are expected per the snapshot file in `exampleRepo.test.js.snap`. wchargin-branch: create-example-repo-command |
||
|---|---|---|
| .. | ||
| jest | ||
| env.js | ||
| paths.js | ||
| polyfills.js | ||
| webpack.config.backend.js | ||
| webpack.config.dev.js | ||
| webpack.config.prod.js | ||
| webpackDevServer.config.js | ||