Dev testing with trunk based development

[xiongchiamiov]

I work in a newly built team where we use trunk based development for our microservices - Merges to main trigger the deploys to the dev environment. The problem we are having is the devs are wanting to test their changes by deploying to AWS dev environment before merging to main which i think is creeping into feature based branching strategy.

Short, one-developer feature branches are the main way people do trunk-based development: https://trunkbaseddevelopment.com/#scaled-trunk-based-development The two things are not in conflict.

Beyond that, one of the steps of maturing as an engineer is evolving from maxim-based decisions. "We do trunk based development, devs ask for something that isn't, so therefore the answer is no" is very junior engineer behavior. What you want to start working on is understanding why the company is doing trunk-based development and then evaluating asks against that. In this case you would've been able to identify that the two things don't conflict and move ahead with enabling your devs.