Skip to content
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.

ciflow/default should not be automatically applied for PRs that are submitted using ghstack #79

Open
seemethere opened this issue Nov 23, 2021 · 0 comments
Labels

Comments

@seemethere
Copy link
Member

Since ghstack creates PRs for every commit in a commit history there's potential for a large inflow of PRs to suddenly be created all requiring CI which puts a strain on our overall CI system.

We should make it so that if a PR is created using ghstack then it doesn't automatically get the ciflow/default label applied meaning the user who submitted the PR needs to explicitly label their PR to enable CI

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant