Hi @DrCray,

I really appreciate your suggestion; it's a great idea :)! While it ultimately depends on GitHub's decision and timeline for implementing such a feature, there are at least two helpful workarounds that can help users with the issue you just mentioned:

1. Use a Git client: Instead of relying solely on the web interface, consider utilizing a Git client such as Git command-line tools or a Git desktop client like GitHub Desktop or Sourcetree. These tools offer more control over the commit process, allowing you to stage and commit changes locally before pushing them to GitHub. This way, you can ensure that all files have been successfully uploaded before initiating the commit.

2. Create a new branch in your repository: Instead of committing directly to the main branch, consider creating a separate branch for your changes and tests. This approach enables you to make multiple commits and refine your changes without affecting the main branch. Once the alternative branch is working well, then the files are ready to go, and you can merge the branch into the main branch.

I hope these are useful suggestions for other users facing the same problem.