Home/ Questions/Q 36957
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T14:28:29+00:00

In my current environment, we have a clean build machine, which has an exact

  • 0

In my current environment, we have a ‘clean’ build machine, which has an exact copy of all committed changes, nothing more, nothing less.

And of course I have my own machine, with dozens of files in an ‘in-progress’ state.

Often I need to build my application with only one change in place. For example, I’ve finished task ABC, and I want to build an EXE with only that change.

But of course I can’t commit the change to the repository until it’s tested.

Branching seems like overkill for this. What do you do in your environment to isolate changes for test builds and releases?

@Matt b: So while you wait for feedback on your change, what do you do? Are you always working on exactly one thing?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. So you are asking how to handle working on multiple ‘tasks’ at once, right? Except branching.

    You can have multiple checkouts of the source on the local machine, suffixing the directory name with the name of the ticket you are working on. Just make sure to make changes in the right directory, depending on the task…

    Mixing multiple tasks in one working copy / commit can get very confusing, especially if somebody needs to review your work later.

    • 0