Here's the reply from dependabot team:
We're aware of this issue and planning a fix. The workaround for now is to
> delete the fork and re-create it without enabling Dependabot security
> updates. Dependabot version updates (setup from config file) isn't enabled
> by default on new forks but will
Yup, it's because upstream cpython has this file:
https://github.com/gvanrossum/cpython/blob/master/.github/dependabot.yml
I still think this is a bug (or missing feature) in dependabot. Please +1
that issue!
On Tue, Dec 1, 2020 at 7:52 AM Mariatta wrote:
> Maybe a recent change in
Maybe a recent change in dependabot. This open ticket seems related
https://github.com/dependabot/dependabot-core/issues/2804
On Tue., Dec. 1, 2020, 7:36 a.m. Guido van Rossum, wrote:
> I got this too on two forks of cpython. It smells like a dependabot
> mistake.
>
> On Tue, Dec 1, 2020 at
I got this too on two forks of cpython. It smells like a dependabot mistake.
On Tue, Dec 1, 2020 at 04:59 Terry Reedy wrote:
> This morning I woke to find that dependabot had added two new branches
> to my cpython fork
> https://github.com/terryjreedy/cpython/branches
> and had created
