At current rate of growth, by 2030 you won't be a real open source project unless you have 6,000 text files in your top level directory. package managers, build systems, meta managers, transpilers, CIs, linters, coverage analysis, issue templates, license automations, ...
-
-
Eew no. My policy is that none of this goes in dev tree. A CI job is a *separate* repo that consumes the repo it's building.
1 reply 0 retweets 1 like -
Not only does this keep things clean; it also ensures the CI has to deal with any issues another consumer integrating the sw would have to deal with.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
It's a great idea, but it seems to break at-scale in the face of GitHub monoculture combined with cargo-culted side cultures like travis ci. We can't convince a million developers to stop dropping config files in the "well known location" of their top level project root.
1 reply 0 retweets 0 likes -
Replying to @mattsta
It's going to crash and burn when those monocultures do...
1 reply 0 retweets 1 like
History of what random ephemeral CI or hosting service you used doesn't belong tied to history of development.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.