Is there a reasonable git workflow when using blueprints? I know you can diff blueprints in the editor, but how about when you do pull requests and such?
The ideal workflow is to “check out” the blueprint. since they’re binary files it means its all or nothing with them.
I use perforce, so not sure how it works in git. But the workflow with blueprints in source control is to lock the file while you work on it, so no one else can change it.
If 2 people want to work on the same blueprint, one goes first, makes his changes, the second person then gets that version and makes his changes after.
If you want to save time, you can “prototype” the changes on a copy or placeholder file, and then manually just copy over what you did.
1 Like
Didn’t mean to double post this, the answer hub was giving me trouble.