need a suggestion: MMT managing branches locally

[ids]

I have multiple branches in a store and use MMT. How might I manage the branches locally when I checkout the branch? What would be a best practice or rule-of-thumb?

Scott

[Nick]

On docs.miva.com/template-branches/template-branches-overview there is workflow that is outlined for using local files.

Also, within MivaLearn there is a learning path called 'Template Branches and MMT' which includes a video walkthrough of the workflow.

Please reach out if you need access to the MivaLearn learning path.

Talk soon,
Nick

[ids]

Thanks, Nick. I forgot about that video. I also hadn't initially thought about it as a real-world workflow. But, if it isn't, it's close.

There are other questions now. One would be, regarding workflow, how to add a "push" note to each item being updated. I made different changes to a number of templates and the note is the same for each when different changes were made to each. What is the suggestion for this scenario?

Scott

[Nick]

Currently that is not how MMT works as it can only add a note per changeset and not per change. The only option would be to push every time you make a change. Is there a reason why it is needed or wanted?

[ids]

It's very possible that multiple changes happen during an edit session without doing an MMT PUSH.
The reason: If I make a change to BASK and ABUS that aren't related but done at the same time during the push, I think the same note gets added to both pages. Am I seeing that correctly?

Scott

btw: I am doing a push, usually, after every change.