stef-levesque / vscode-perforce

Perforce basic commands for Visual Studio Code
MIT License
75 stars 102 forks source link

Changelist selection #22

Open markpeterfejes opened 8 years ago

markpeterfejes commented 8 years ago

Hey!

It would be really-really useful if we could select a changelist, or set a default changelist where deleted/edited files go

Thank you very much!

stef-levesque commented 7 years ago

Now supported. Please update to version 2.0.0

markpeterfejes commented 7 years ago

I don't really get how can I select a default changelist for checked in files. Can you help me with this please? :)

stef-levesque commented 7 years ago

Sorry, I misunderstood your request.

The extension currently follow the same behavior as P4V, which mean all newly added/edited files go to the default changelist, where you can then moved them to other changelist, or create a new one.

dolphy01 commented 7 years ago

this feature would still be of use: select a named changelist which checked out files will be automatically added to (with the changelist itself automatically created if it doesn't exist)

alternatively, the ability to submit the default changelist would be even better. the workflow currently requires changing a file, manually creating a new changelist, manually moving those files to the new changelist, and submitting the new changelist. for fast iterative changes, the ability so simply submit the default changelist would incredibly useful.

let me know if this doesn't fall within this feature request, and I'll write a new one.

jel-massih commented 7 years ago

If you can create a separate issue for the "Submit Default Changelist" feature that would be awesome. Probably try and get it to mimic P4V behavior where you enter a name for the CL.

dolphy01 commented 7 years ago

Feature request submitted: #72

nagarsuresh commented 7 years ago

there should be a way to select a CL and every edited file goes to that CL something similar to what Intellij does where i can mark any one given CL as "active".