We’re slowly rolling out extra features that are enabled by installing the GitHub App (syncing state, CI status, author, assignee, labels) without needing repo scope, that’ll be free for open source repos and paid for private.
Didn’t expect to see this on HN news today, the homepage will be updated within the next day or two to explain the paid feature.
Octobox maintainer here, we’ve done a lot of work recently to make Octobox work better and fast for power users. I’ve heard that Shopify is using it to handle very high volumes of notifications and seem to be happy users.
We just launched this new podcast where we explore the technical details of package management, the stories and the history of various projects, and the communities around them too. Every two weeks there will be a brand new interview with a package manager maintainer.
First episode is an interview with Mike McQuaid, the lead maintainer of Homebrew.
beefsack is right, please do NOT make it a github specific thing. Just one config folder. All config files for services, integration, etc. should go there.
In the config.rc file you could call that folder however you want.
I personally do not like ".meta", because it is not clear what kind of information it may contain. "Meta" might be anything, documentation, description, website, design papers, everything is meta. It is a bit like using "Information" as a menu entry for a website.
How about we put each individual config file in its own individual directory? We could name the directory after the file too, so that it is clear where each file is ;)
No but seriously, I don't think this mess of config files in the project root is really a big deal. I already grouped the interesting stuff under /src. If it is a big deal, then lets hash out an RFC that covers the general concept of "configuration" once and for all and be done with it.
reply