Revision control

Split by whether they change your project. Read-only tools are always safe to try.

Reading

• Check Writable — Can this asset actually be saved? Distinguishes read-only, provider-not-connected, not-checked-out, and checked-out-by-someone-else, because each needs a different response. Worth calling before a run of edits on an asset.
• Source Control Status — Which revision control provider is configured and whether it is actually connected. CHECK THIS BEFORE A SESSION OF EDITS: if a provider is configured but not connected, files are read-only and everything you change will be lost at save time.

Writing

• Checkout — Check out an asset through whichever revision control provider is active, and verify it became writable. Works with Perforce, Git, Plastic and Subversion alike. Note this is a change to SHARED state - it tells your team you are editing the file.