This is a very interesting service, thank you! May I ask you for some little thing that might change the (development) world? Would you please like to introduce a folder, where people might put their dependency.yml file - this is an effort to finally stop the spreading cancer of "put one more config file into the project root". I would like to suggest to call that folder simply "config" - all the projects and tools o…
Show HN: Dependency CI – Continuous testing for your dependencies
21–30 of 64 posts
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#22Great work on this, looks very useful. Does it only work with GitHub? Would love to have this for my private GitLab instance
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#23This is a very interesting service, thank you! May I ask you for some little thing that might change the (development) world? Would you please like to introduce a folder, where people might put their dependency.yml file - this is an effort to finally stop the spreading cancer of "put one more config file into the project root". I would like to suggest to call that folder simply "config" - all the projects and tools o…
Agreed, I'll definitely the ability to move your dependencyci.yml file into a .github folder like the issue and pull request templates: https://github.com/blog/2111-issue-and-pull-request-template...
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#24This is a very interesting service, thank you! May I ask you for some little thing that might change the (development) world? Would you please like to introduce a folder, where people might put their dependency.yml file - this is an effort to finally stop the spreading cancer of "put one more config file into the project root". I would like to suggest to call that folder simply "config" - all the projects and tools o…
I've thought of the same thing, but I feel that the horse has well and truly bolted, run back through the barn a few times, kicked some shelving over and then continued out the front and over the horizon at a brisk pace.
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#25Earlier quoted context omitted.
I've thought of the same thing, but I feel that the horse has well and truly bolted, run back through the barn a few times, kicked some shelving over and then continued out the front and over the horizon at a brisk pace.
The ideal solution is a migration path; retain support for config in project root, but check a configuration directory first.
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#26This is a very interesting service, thank you! May I ask you for some little thing that might change the (development) world? Would you please like to introduce a folder, where people might put their dependency.yml file - this is an effort to finally stop the spreading cancer of "put one more config file into the project root". I would like to suggest to call that folder simply "config" - all the projects and tools o…
Agreed, I'll definitely the ability to move your dependencyci.yml file into a .github folder like the issue and pull request templates: https://github.com/blog/2111-issue-and-pull-request-template...
Thanks again!
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#27Everyone else - Is this a general problem with people locking these (very cool) tools to GitHub? Is there a generalised solution to the problem of source control integration?
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#28Re: Show HN: Dependency CI – Continuous testing for your dependencies
#29Great work on this, looks very useful. Does it only work with GitHub? Would love to have this for my private GitLab instance
Yep. Same for Bitbucket. Or just support all git repos that are accessible via the public internet. Github's pricing model means that lots of people can't use it for private repos - 'per repo' pricing isn't fun if you prefer lots of small repos.