Jump to content

BDG

Members
  • Posts

    3
  • Joined

  • Last visited

BDG's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. I should add, that even if I take the approach labelled (1) above, in this case I didn't actually want to apply the change to that file, I believe this is a valid use case for the shelve functionality regardless of locks involved.
  2. Hi, I think there's been a miscommunication, the problem is that I cannot apply changes from a shelve if that shelve contains changes to a locked file, the Plastic client literally does not allow me to perform the operation, hence the need for a partial "Apply Changes" operation from the "Cherry pick from changset [...]" view. The only way I can find to apply a shelf if one of the involved files is locked is either: get the person who checked it out to check it in, or to break the lock manually with cm, which undermines our entire workflow and creates more issues What I'm asking how to do, or requesting if the feature does not exist, is to select a subset of the changeset in the "Cherry pick from ..." view (the view after pressing "apply shelve in my workspace") and "Apply Changes" would apply only those changes, so that I can ignore the changes to the locked file. I imagine the operation behaving similarly to how I can select a subset of files in the pending changes view to checkin.
  3. Hi there, loving Plastic so far, but there are a couple of operations that seem like they should be easy to accomplish but aren't immediately obvious. Here's the scenario I currently have, and I'd like to know what the best way to go about fixing. I made a bunch of changes a couple weeks back on a feature, but had to shelve those changes to work on something else. No problem here, the shelve feature works exactly as it should. Yesterday one of our team members checked out a level asset, this is a pretty central asset to what we're doing right now, and they forgot to check it back in at the end of the day. It happens, not a big problem. However, that file is in the changeset I shelved a couple of weeks ago. Now those changes I made to that level asset aren't really important and easy to recreate in the newer version of the level after my coworker checks it back in later today. BUT, I can't seem to figure out how to selectively apply a subset of the shelve changeset, ie. everything but the level asset. This, in my opinion, is an absolutely essential feature of any shelving/stashing functionality. Afaik shelving is still a relatively new feature for Plastic so I'm guessing this functionality hasn't been exposed to the core toolset and GUI yet? I'd like to know if this is on any internal roadmaps, and how to achieve it non-destructively (ie. not breaking locks) in the meantime.
×
×
  • Create New...