Deploy to heroku and mass commits, how to avoid?

Question

git

When publishing a Django app to heroku, I fix occasional bugs. For example , in the settings.py file, or yesterday with collectstatic it could not find the Bootstrap fonts, after googling I found a solution, everything was fixed .
The problem is that the heroku cli does not see the fixes and, accordingly, the error remains until you do a git commit. I ran into a situation where there can be a lot of commits, and after pushing not to heroku, but to the master branch (on bitbucket), all these essentially meaningless commits are added (when I need to commit something in essence).
Even though I'm following the heroku instructions, can you explain what I'm doing wrong? How to ignore edit commits made to heroku when pushing to a working branch?

Answer 1

You almost have gitflow.
Small but gitflow.
Work with branches.
Distinguish commits with minor fixes to the dev branch, for example.
And already the production / master branch - let it fly to Heroku.

Answer 2

you work on one branch, run changes, edit thousands of commits, and deploy from it to a test heroku.
when it comes to putting it into the master, you squash all the little things, comb the commits and all that. and to the master. it on github or wherever you have a master;)