Please remember to never include secrets in code this includes webhooks, usernames and passwords. You will not be given any sensitive information and should create anything you need for testing (discord server, replit repos etc.) GitHub uses environment variables to store these, please be aware of how you intend to get these out of the environment (such as via a file or asking the command line).
[ ] Start by creating a single repl (replit repo) with no user interaction
[ ] Add ability to create any number of repls
[ ] Get the number of repls that should be created from a command line argument
[ ] Add a filter that should be supplied before the number of repls to create. This filter should have no spaces, not cap sensitive and begin with a dash (-) if a single character, or two dashes (--) if more than one character. (eg --CLA or -C)
[ ] Created repls should follow a human readable naming convention in which each new item is unique. (Assume code is ran fortnightly.)
[ ] Write unit tests to test each "unit" aim for at least one for each function, preferably 2-4.
[ ] Write integration test(s) (AKA system test or end to end test) to test the complete system.
Please remember to never include secrets in code this includes webhooks, usernames and passwords. You will not be given any sensitive information and should create anything you need for testing (discord server, replit repos etc.) GitHub uses environment variables to store these, please be aware of how you intend to get these out of the environment (such as via a file or asking the command line).