Community
Participate
Working Groups
When I have multiple changesets active in the Synchronize view it happens from time to time that a commit comment consists of several tasks. In my case I frequently have certain changes in my workspace that I don't want to commit (temp changes to config files etc...). For this purpose I create a local task and name it "DO NOT COMMIT". As I said above, from time to time these files get also committed (be it my fault or not). The real problem for me is that the EMFT build scripts generate the release notes out of the commit comments and for my local task there appears a "[1] ..." line which the script resolves against the Eclipse.org Bugzilla repository. I'd like to configure a different pattern (from "[\d+] ...") only for the local tasks, so that an accidental commit won't mess up my release notes (which is really hard to fix in the CVS *,v files.
Eike, can you please give more details how does it happen that your "DO NOT COMMIT" changeset gets committed? The only way I know is to select it in Synchronize view and run commit and then there is dialog showing commit comment again. It is now possible to configure commit templates per project, but not per task repository. I often use local tasks when need to prototype something, but those tasks can be related to various projects and per-repository templates simply won't work in that case. However, current pattern used for local tasks doesn't make much sense either: "Incomplete - task 342: Some task" (see for example history for org.eclipse.mylyn.releng/3.3/config/build.sh), because "task 342" in that case is a local task only existed in committer environment
As I said, it can be my fault or not, I'm not sure sure after the fact. May be I clicked the wrong button (commit all changesets, which I'd like to disable at all but this is not your arena). Sometimes I got the *feeling* that a file slips into multiple changesets and on commit of one of them both changeset comments get committed. BUT: that's only a feeling, I didn't have the time to proof it yet ;-( and this evening I go to vacation ;-) In either case it would be very helpful to have the comment templates configurable on a per repository basis. I guess it's some work but it won't be complicated, will it?
Eike: we have this support in the latest weekly build, so it would be great if you could try it out. http://www.eclipse.org/mylyn/downloads/ In addition to Eugene's comments, note that you can manually create a change set called "DO NOT COMMIT" via the popup menu in the Synchronize view. I only do this in the Eclipse that I launch my working workspace from, so you approach with local tasks probably makes more sense. *** This bug has been marked as a duplicate of bug 157342 ***
