I’ve been using GitHub’s web interface to make changes to my project files directly in the browser. The problem I’m running into is that whenever I finish editing a file, it forces me to commit that single change right away. This means I end up with tons of small commits when I really want to group related changes together. Is there any way to edit several files first and then bundle all those modifications into one commit? Having so many tiny commits clutters up the project history and makes it harder to track meaningful changes.
Unfortunately, GitHub’s web editor doesn’t support staging multiple file changes before committing - it’s designed for quick single-file edits rather than comprehensive modifications. Each edit through the browser interface requires an immediate commit, which is exactly the limitation you’re experiencing. For grouping related changes into single commits, you’ll need to work locally with Git. Clone your repository to your machine, make all your desired changes across multiple files, stage them with git add, and then create one commit with git commit. After pushing back to GitHub, you’ll have the clean commit history you’re looking for. The web interface is convenient for minor tweaks but becomes counterproductive when you need proper change management across multiple files.