We've tried to activate or update your repository on Depfu and found something odd:
While you seem to have a CI service that builds your main branch, it looks like it's not building
our depfu/* branches.
Without a service that will test the Depfu branches, we can't guarantee you that
incoming updates of your will actually work with your dependencies. We think that this degrades the
service we're trying to provide down to a point where it is more or less meaningless.
What you can do now
If you're using Travis-CI make sure you'll include the depfu branches in your branch whitelist in
your .travis.yml like so:
branches:
only:
- master
- /^depfu\//
The same is possible for CircleCI, which is documented here.
If you're using a different service or a self hosted solution like Jenkins, please refer to their
documentation on how to build additional branches.
It might be necessary to once deactivate and reactivate your project in Depfu for the CI service to
be properly detected.
If you don't want to set up CI properly for your project, please deactivate the project in Depfu, as we can't
do anything for you in this case.
Hello,
We've tried to activate or update your repository on Depfu and found something odd:
While you seem to have a CI service that builds your main branch, it looks like it's not building our
depfu/*branches.Without a service that will test the Depfu branches, we can't guarantee you that incoming updates of your will actually work with your dependencies. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
What you can do now
If you're using Travis-CI make sure you'll include the depfu branches in your branch whitelist in your
.travis.ymllike so:The same is possible for CircleCI, which is documented here.
If you're using a different service or a self hosted solution like Jenkins, please refer to their documentation on how to build additional branches.
It might be necessary to once deactivate and reactivate your project in Depfu for the CI service to be properly detected.
If you don't want to set up CI properly for your project, please deactivate the project in Depfu, as we can't do anything for you in this case.
How to deactivate the project
If you think that this is a mistake
Please let us know by sending an email to hi@depfu.io.
This is an automated issue by Depfu. You're getting it because someone configured Depfu to automatically update dependencies on this project.