same, we haven't settled on a branching/environment strategy either, we're kinda following a gitflow between a development , QA, and Production accounts. • developers will create a

feature

branch off of

develop

, to develop and validate in a development account • it should be merged back into

develop

to resolve conflicts, and QA will test this in a separate QA account (which should match production, (or at least be very close)) • a

release

branch is created, then merged into

master

and back into

develop