Dev Branch Behavoir Poll

[Bruce - PhosphorMedia]

I know Brennan and team are working on Dev Branch improvements--some of which address part of what i'm asking here, but...this also goes to 'intended behavior' which might improve overall dev branch usage.

The question is:

"Should the admin reset to use the Primary branch after logging out?"

My vote is 'Yes'.

[Brennan]

Hey Bruce,

Do you often find you login and don't realize you're still on a different branch? Or do you just prefer to always be on Production and have to change it each time? We probably can add a setting, just trying to better understand your issue.

[lesliekirk]

Hey Bruce,

Do you often find you login and don't realize you're still on a different branch? Or do you just prefer to always be on Production and have to change it each time? We probably can add a setting, just trying to better understand your issue.

I've just recently had a storeowner have the most difficult time getting out of the dev branch back to the primary branch. I have had other store owner complain of being "stuck" in the dev view beside this one.

If there were a way to reset back, that might be a huge plus.

[SidFeyDesigns]

Even a setting that switches the branch to primary on log out would be nice.

Maybe add a tab called "Template Branch Settings" within User Interface > Global Settings.

Put a checkbox in that tab to "Switch to primary branch on Log Out".


It would also be nice to be able to choose certain things to NOT be branch specific, such as category headers and footers.


Also, in the branch template history/merge changesets area, it would be really nice if the page template or theme component code was appended to the end of the note when you add a note.

I know this can be manually typed but it can be easy to forget when adding a note to any templates / theme components when making changes.

When you don't manually add a template code or some sort of identifier to the end of your note (ex: Change container div classes for <mvt:item name="hdft" param="header" />: CTGY) it can make it hard to roll back to specific change sets if a similar note is added to multiple templates that had similar changes made to them.

[Bruce - PhosphorMedia]

I think its probably 50/50 on a site that's truely in a development phase. However, for sites that are just getting a 'touch-up' or two, that number drops to about 90% of the time I log in, i'm going to be working on the Primary branch. So yea, this is strickly from Develeropers perspective.

[mvasquez]

+1 for this auto-reset. I find that I am switching between so many tasks, and I'll come back to a store and get into something only to find I wasn't in the right branch.

[Leanne]

I also support the branch reset on logout, along with prepending the specific template component being updated to the update notes. I do this manually, but with all things manual there is the possibility of remembering you didn't do that just as you hit the submit button (not that I would know this from personal experience...).