-1 I personally think it's a necessary evil and a good forcing factor to get CI fixed. Before that requirements, things that failed unit tests were being pushed into master daily. It was a big problem. At least now master is stable.
On Tue, Oct 31, 2017 at 12:22 PM, Hen <[email protected]> wrote: > This makes sense to me. CI isn't of value if it isn't continuous. +1. > > On Tue, Oct 31, 2017 at 12:07 PM, Indhu <[email protected]> wrote: > > > Hi, > > > > We have been having issues getting CI to work fast enough. Currently the > CI > > is being the bottleneck to get commits in. This is severely impacting > > development. I propose we disable 'required status check' for the master > > branch so that we can development is not impacted. We can work on fixing > > the CI situation in parallel. > > > > Committer, > > Please vote if you are okay with disabling 'required status check' for > > master. > > > > Once we have enough votes, I'll request a mentor to file a ticket with > > infra. > > > > Thanks, > > Indu > > >
