The Build Forge Reflector plug-in allows you to execute pre-flight runs of Build Forge projects. Without checking code into your source repository, you can substitute specific files from your local machine into a code tree, then run a Build Forge project against the combined code tree, and get the results.
To do this, you need to configure the plug-in for each IDE project, letting the plug-in know which local files should be copied to the Build Forge server, and where in the Build Forge project the copying should occur.
After you configure the system, you can launch a run via the Execute Build Forge Project menu option. The plug-in then communicates with the Build Forge console to launch the Build Forge project, and copies the files you specified from your local filesystem to the server running your Build Forge project, before it runs a specified step.
Using this system, you can inspect a Build Forge project, which typically includes some early steps which check files out of source control into the project's working directory. To set up a pre-flight execution, have the system add your files after the checkout step, so that your updated files overwrite the copies that came from source control. The result is a Build Forge project run that reflects your local changes, without changing the source repository. If the run produces the results you intended, you can then check your files into source control.