I'm trying to explain our release process to a third party developer who has access to our git repo to avoid publishing changes that haven't been test/approved yet. Could someone give me feedback as to whether this seems like an effective process and is clearly communicated? Is this in line with best practices?