Suggestion - keep all the setup in TC only

[bubenshchykov]

What if we move TC merge script to TC steps, so developers will be pushing their prs to 'ready' ref via pure git? or TC can be triggered by github comments.

Mainly I would like to do a regular git operations, and keep all the auto-deploy setup in one place (TC)
It will also avoid a new 'env installation' step for newcomers.

[ebdrup]

tcmerge is just a very simple helper, it's up to you if you want to use it.
It has the benefit of checking things for you locally, that is also checked on TC. Checking locally gives you much faster feedback, if you forgot to do a PR or you forgot to push your changes to github (and frees up TC for others to use). All of these checks are also done on TC.
Plus it helps you by turning spaces into underscores in the git branch name that is used for the commit message on TC.
But you can easily do the push to the ready branch without it.

[bubenshchykov]

perfect