Count `production/*` as production deploy for cycle analytics
For cycle analytics, I believe we treat the
production environment as a special case, and use it to detect when an idea gets into production. With review apps changes, we now support a slash syntax to group related environments in the list. This is mostly used for
review/<branch> environments, but it's possible for people to have multiple production environments, and someone might then want to group them like
production/us, or even just make it look prettier with
production/www.example.com. In any of these cases, we should treat the first deploy to one of these
production/* environments as a Production deploy.
Links / references