Closed plastikfan closed 4 years ago
Waited for over an hour for initial pull-request, which didn't come, so I reset the app on greenkeeper.io
Added - /^greenkeeper.*$/ to branch config in travis.yml (done on master branch, pushed and the repo reset on greenkeeper.
... It appears that greenkeeper already makes this change on the greenkeeper branch so I don't know what the implications are of make this change manually on the master branch is.
It may be wise to set the default branch on github to be develop until there is a production ready release available. All the activity is going on in develop, so that's where external services/apps should be triggered from during development.
In order for the reset to work, the existing old initial greenkeeper branch needs to be deleted first. For new repos, on the master branch, the greenkeeper branch must be whitelisted in the travis config prior to attempted activation of greenkeeper.
... Actually, david-dm on zenobia-ts is now actually working and provides a more visual service than greenkeeper, so there is value in using both simultaneously. Greenkeeper, does the automated grunt work, and david-dm provides a nicer visual view of the dependencies without attempting to do anything about it; ie, it'smore like the reporter/viewer, whilst Greenkeeper is the manager and fixer. So go ahead and fix up and just allow some time for activation to take effect.
use https://greenkeeper.io instead. david-dm.org is insufficiently documented so don't use that.