[bsder]

That is far more state than most people are comfortable keeping track of. Most people have "working" and "committed" and that's almost more than they can deal with.

Ever dealt with someone who has a specific breadcrumb trail for making changes to WordPress, for example? "Staging" is an extra set of steps to his breadcrumbs that can go wrong.

The staging area is useful to a small number of people like you in return for complicating the life of everybody else.

[wingerlang]

Is it really that much state? For example, the thing I am working on right this moment have the following changes:

1. I changed my environment URL because I need to test on a specific one.

2. My actual feature changes, couple of files and a hundred lines changed.

3. A bunch of debug print messages, some are intertwined within the changes in 2, and some are in other places.

I will stage most of things in 2, probably in multiple commits to group logically. Most of 1,3 will simply be discarded once I comment and test final version. 1, might stick around for the next features I work on.

I can not believe this is too much state, nor can I believe this is not a fairly common workflow for developers?

How would you do this without staging? Would you discard the temporary changes and commit, then possibly write them back manually?

—-

I appreciate the Wordpress example but I’m not familiar with it so it flies right over my head to be honest.