Problem

The new Repository Commit task will commit all files and folders (added or modified) in the repository folder area. By default the Source Code Checkout task is set to the plan build working directory and there is where all the Bamboo tasks for that particular plan will run, creating and modifying files. As a consequence, if the Repository Commit task is used, the plan will end up committing not only modified repo files but any other temporary file that was created during the build.

Suggested solution

Two improvements can be done in this task to help the users:

1. Add a check box that will allow the user to disable the addition of new files.
   This would allow users to create new files in the repository area and they would not be committed. Only modification of existing files would be possible.
2. When a commit task is added a warning will show up explaining that the Source Code Checkout task should be set to a different location (in case it is set to the plan build working directory). This would prevent problems with any other tasks that might create temporary files that should not be added to the source repository.

Workaround

Every time you use a Repository Commit Task, make sure you set a special folder for the the repository checkout. This can be achieved by setting the Checkout Directory field on your Source Code Checkout task.