Discussion has died down, I think the consensus is to use Dependabot. I
will proceed with allowing it access.
Thanks,
Matti
On 29/8/19 12:07 pm, Nathaniel Smith wrote:
AFAICT all these services work by creating branches inside your repo
and then making a PR from that – they don't make their
AFAICT all these services work by creating branches inside your repo and
then making a PR from that – they don't make their own forks. (Which makes
some sense when you consider they would need tens of thousands of forked
epos for all the projects they work with.)
I don't think there's any need to
Hi,
The answer to why Dependabot needs write permission seems to be to be able
to work with private repos:
https://github.com/dependabot/feedback/issues/22
There doesn't seem to be any way around it... :(
Ryan
On Thu, Aug 29, 2019 at 12:04 AM Matti Picus wrote:
> In PR 14378 https://github.c
I’m confused about why it needs write access to code... if I were doing this
for scikit-image I would possibly clone the code to a new repo.
> On 29 Aug 2019, at 8:03 am, Matti Picus wrote:
>
> In PR 14378 https://github.com/numpy/numpy/pull/14378 I moved all our python
> test dependencies to
In PR 14378 https://github.com/numpy/numpy/pull/14378 I moved all
our python test dependencies to a test_requirements.txt file (for
building numpy the only requirement is cython). This is worthy
since it unifies the different "pip install" commands across the
diff
