-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: label creation and attachment #168
Comments
HI, |
Well, the requirement is that all the checked-in files related to an issue are labelled with the same id. That's why I think a good option, that wouldn't interfere with other workflows, is to accept a label as optional input to the check-in command. |
Ok. I will try to integrate such a feature and will provide a prerelease for you to test. |
Hi @mgrojo , |
Thank you for this! I'm a bit confused, because it seemed to work good in a file, but not in later files that I tried. I don't see any error either. The file is checked-in but the label that I provided to the new prompt is not attached to the file version. How can I investigate this? |
Hi,
Thanks for this extension, it is working better for me than the official IBM version because I cannot use CCRC.
One important feature of ClearCase that I miss is creation of label types and attachment to versions. Specifically, to files just checked-in.
A workflow that I like is creating a label type with an appropriate comment for the task, and then (I was doing this with the help of a script) attaching the label to every checkout done in the view and assigning that comment to the checkout. You could implement it with new operation to create the label type with a comment. Then in the checkout operation a prompt for an optional label, and you checkout the file with the label comment and attach the label. In the check-in operation, the comment is left as is if the user leaves the comment field empty and also leave the labels of files that already have it.
Another option, which might be easier to implement, is to add another field to the "check-in" dialog for an optional label. The label type is created if not existing (maybe after user confirmation) and the label is applied to all the files checked-in. The drawback is that you cannot reuse the comments in the checked-out files.
The text was updated successfully, but these errors were encountered: