title: How to properly maintain one commit per feature branch strategy in a GIT workflow?
body: <p>In a project I am working on, we have workflow of one commit per feature branch. If I have not to make any subsequent changes after a commit, then it is fine, but if after a commit, and which has been pushed too to remote, I have to make some changes, how to make sure there still is one commit in that branch? I am currently using git commit --amend but that changes commit hashes. Is there a way that I still have one commit and the commit id is not changed? or what is the best approach/alternative to using git commit --amend? Or amend should be fine?</p>
  <p>Regards</p>