IssueRaiser

Feature request: Ignored branches for deploy previews

Hi there! Zeit deploy previews are awesome, it's definitely an essential feature for our workflow at Open Collective. We're using a tool called Crowdin to manage our translations. This tool creates a lot of commits, sometimes hundreds in the same day (see https://github.com/opencollective/opencollective-frontend/pull/2824). Deploys preview don't really matter for the pull requests created by this tool and we would prefer to not flood our Zeit pre-deploys with it. **Proposed solution** In `now.json`, add a `deploy-previews` fields that would accept an `exclude` parameter like this: ```json { "version": 1, "name": "opencollective-frontend", "type": "docker", "deploy-previews": { "exclude": ["i18n/crowdin"] } } ``` Now would then not deploy any branch matching the names given in this array. Bonus: allow wildcards in names (ex: `i18n/*`) - not required in our use case, but could be nice.

Posted by Betree on Oct 17, 2019, 10:14 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments

github (Software)

Feature request: Ignored branches for deploy previews

BetreeOct 17, 2019, 10:14 AM

Hi there! Zeit deploy previews are awesome, it's definitely an essential feature for our workflow at Open Collective. We're using a tool called Crowdin to manage our translations. This tool creates a lot of commits, sometimes hundreds in the same day (see https://github.com/opencollective/opencollective-frontend/pull/2824). Deploys preview don't really matter for the pull requests created by this tool and we would prefer to not flood our Zeit pre-deploys with it. **Proposed solution** In `now.json`, add a `deploy-previews` fields that would accept an `exclude` parameter like this: ```json { "version": 1, "name": "opencollective-frontend", "type": "docker", "deploy-previews": { "exclude": ["i18n/crowdin"] } } ``` Now would then not deploy any branch matching the names given in this array. Bonus: allow wildcards in names (ex: `i18n/*`) - not required in our use case, but could be nice.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue