When working from different machines, files that are checked out by me don't get set as writable

[sinisastevanovic]

So this is happening quite often in our team.
We are all working from different locations (home office, office) each day.
Example: Say I am working on a feature where a few files are checked out. At the end of the day I push my changes but want the files to stay checked out, so nobody can edit these files. If I am changing the machine I am working on I pull my changes and continue working on these files. Now I can't save them because they are all read only.

Would it be possible to automatically make these files writable if the username is the same as the one who checked out the file?
Manually making all these files writeable is tedious.

Oh and thanks for this Plugin, it really made all of our lives easier!

[mastercoms]

Ah, that's an interesting use case, thanks for letting me know!

[mastercoms]

Just as a note, this use case is supported in PBSync which manages locks before editor launch. But I should add these features to the plugin for better usability.

[sinisastevanovic]

Thanks for the heads up!

[adrian-j-programmer]

Any update on getting this in? My team is about to start using this plugin and this issue might hit some of us. I for sure use different machines even during a single day, and would like to be able to pick up my work without running into locks issues.

[mastercoms]

Still thinking about the best way to approach it, but we've gotten a better design for managing read only status recently, which should be able to support this work better