clean commits
For Preparing a Git Repository for University Submission, the clean commits step needs a visible outcome. If you cannot describe success or failure, reduce that step further before continuing.
A Git submission should demonstrate that the repository can be reproduced from a clean state. The important points are meaningful changes, a useful README and removal of secrets or local machine files, not the largest possible number of commits.
Before submission, clone the repository into a new folder or clean environment. Run the documented build and tests. This exposes missing files and local dependencies before the marker encounters them.
Do not treat Preparing a Git Repository for University Submission as a rigid checklist. Pick the first point that is unclear in your own work, test it with one concrete example, and only then move on.
For Preparing a Git Repository for University Submission, the clean commits step needs a visible outcome. If you cannot describe success or failure, reduce that step further before continuing.
For Preparing a Git Repository for University Submission, the check the README step needs a visible outcome. If you cannot describe success or failure, reduce that step further before continuing.
For Preparing a Git Repository for University Submission, the remove secrets step needs a visible outcome. If you cannot describe success or failure, reduce that step further before continuing.
For Preparing a Git Repository for University Submission, the run a clean build and tests step needs a visible outcome. If you cannot describe success or failure, reduce that step further before continuing.
files exist only locally and were never committed
API keys or passwords remain in repository history
the README documents an outdated launch command
the build works only because packages are installed globally
Close Preparing a Git Repository for University Submission and explain your next step in your own words. State the assumption, expected result and the test you will use for that specific step.