# Two different environments workflows (auto generated after the Add New App process)
**URL:** https://discuss.bitrise.io/t/two-different-environments-workflows-auto-generated-after-the-add-new-app-process/1736
**Category:** Website
**Created:** [May 15, 2017, 10:49pm UTC](https://discuss.bitrise.io/t/two-different-environments-workflows-auto-generated-after-the-add-new-app-process/1736 "2017-05-15T22:49:32Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@miguelfreitas](https://discuss.bitrise.io/u/miguelfreitas)
#### Post date: [May 15, 2017, 10:49pm UTC](https://discuss.bitrise.io/t/two-different-environments-workflows-auto-generated-after-the-add-new-app-process/1736/1 "2017-05-15T22:49:32Z")
It would be amazing if you create by default when I add a new app, two different workflows: 1 for test and other for production environments, connected respectively to develop and master branches. For example, for Android, beside this it would be amazing create for these 2 environments different things:
- GRADLE\_TASK : assembleDebug (test) / assembleRelease (production)
- 2 keystores: 1 for test other for production
- 2 triggers: push develop branch → triggers test workflow, push master branch → triggers production workflow
Thanks,
Miguel
---
### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [May 16, 2017, 9:02am UTC](https://discuss.bitrise.io/t/two-different-environments-workflows-auto-generated-after-the-add-new-app-process/1736/2 "2017-05-16T09:02:12Z")
Awesome idea and we do plan to do something like this!
One note/question: do you need a keystore for debug/test? In general for that most projects just use the default Android debug keystore.