Jump to content

Oyvind

Members
  • Posts

    3
  • Joined

  • Last visited

Oyvind's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare

Recent Badges

1

Reputation

  1. I also wanted to comment on this as I find this fairly important to me, even though Mikael went over it above. With Git, you have the opportunity to either stage (selecting what you want to submit for a commit) or undo individual lines or hunks (blocks of code, similar to how the Diff window presents all changes as many smaller groupings). That made it very handy if you had been, say, debugging a problem and had added bunch of temporary logs during the process when trying to hunt down the issue and solve it. After I'm done with that process, I would then ideally just checkin the actual changes that are relevant to the issue and then revert all the other changes that wasn't meant to be persistent. With Git that's fairly easy as you'd then just select the line(s)/hunk(s) that are relevant, then undo the rest of the file. Or if there are many changes and I just want to undo a line or two, I could also do that instead. You can see a simple example of this with visual tool (in this case, Git Gui) here : http://nathanj.github.io/gitguide/committing.html As far as I can see with Plastic, this isn't possible and you're forced to go back into the text editor/IDE and undo the changes there. Edit: Just discovered that the Rider plugin (which I had yet to try out) does support the functionality to revert a changes when diffing it, which at least helps. Would still be handy if this could be available inside the diff window
  2. Heya I wasn't able to find anything concrete regarding this topic, so figured I'd ask and see if there's something I've missed. What I'm trying to do, is that I want certain groups and/or users to be able to view and get updates from a repository but prevent them from checking out any/specific files. As an example, I have a third-party user that I want to give access so they can get the latest changes and test locally, but disallow them from affecting the files in any way, which in this case includes locking. I've tried setting up a test scenario where I gave the user only allowed permissions for Read and View, so that they'd be able to find the repository and download it. On everything else I tried putting Denied as enabled, but even with this the user is able to check out files, which could potentially disrupt work if that means having to either contact the user or to jump into terminal to manually unlock the file(s) in question. I figured that maybe the ci or configlocks permission would be the relevant ones, but that doesn't seem to be the case from what I've tested Appreciate any helps on this matter
  3. I was also confused when using Plastic's built-in merge tool first time around, didn't realize that the buttons existed the first time I tried the tool. Went as far as deciding to try and replace the built-in tool with what I was familiar with from Git, but after having issues with resolving the parameter values, I ended up going back to try the built-in one again and only then I figured out that there were actual buttons. My impression was the same as JEP in that I thought the fields were just titles
×
×
  • Create New...