Select changes which you want to commit
When you as developer changes multiple files which belong to different stories, you want to keep changes that belong to the same story in 1 commit.
This gives you the possibility to later on only deploy these changes.
It makes it also better to follow change log.
Solution
Be able to select or deselect the changes you want to commit or don't want to commit.
This is possible in GIT by only staging certain changes to the commit.
@Kevin, I understand the use case for 'staging & committing specific changes'. This is a pattern I also follow myself in traditional coding, and I see how it helps getting cleaner commit messages which is also something I can only applaud. The advantage of this feature is definitely clear.
The potential disadvantage is a possible increase of accidental consistency errors, but perhaps that's something we could also check before committing, or maybe there are other solutions to this.
If this idea gets more traction and/or if I hear it more often during conversations, we're definitely open to considering implementing this and figuring out how to best do so.
Until that point however, we don't have a lack of topics for the Version Control roadmap, and we're choosing for other topics (such as Visual diffing) that do come up in nearly all conversations.
Bottom line: I'm not rejecting the idea and see it could bring value, but it does require some design efforts (as well as engineering efforts) that we're not willing to do at least this calendar year.
@Tom, I can fully understand your remark, but why not postpone pulling the latest version from the server until all files are committed.
In most usecases, i just want to create them separately to link the right stories and to have a clean commit message. In that case, I want to do two commits right after each other and pull after the last commit is done. In that case, you should minimize the consistency errors right?
What a great idea, I wonder if they add this to the platform soon.