[Subclipse-users] workflow improvement suggestion

I often work on my code in a checkout of the trunk, updating now and
then to keep up to date with developments on the trunk.

However we don't commit directly to trunk in my organisation, generally
we create a job in our ticketing system, and then create a branch for
the ticket with the code to submit to QA.

I often find myself repeating these steps: branch from trunk and switch
to the branch, commit the changes, then switch back to trunk.

It occurred to me that it would be fairly straightforward to automate
this within subclipse. It already has a helpful command that lets you
branch from your current working location and switch to the branch. If
there was another command that also did those steps, but also committed
all the changes to the new branch, and then switched back to the
original branch, it would be a great time saver!

Just a thought.

Cheers
Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-05-21 08:36:47 CEST