Jon Pretty

Suppose you set up a repository that accepts any PR that passes CI. You forbid CI changes, but the rest of the codebase is fair game. What sort of testing, linting etc would you configure for CI?

i would create a separate repository with separate access controls with the testing for the repo, where any changes to the test repo then get synced to the main repo. in that test repo, i’d probably incorporate testing against a rigid specification if possible

this is actually something i’ve wanted to dig into since i learned about the fury build tool from @propensive — one of the ideas is linking tests and documentation in a separate repo, so tests and docs that cover the code for a given commit can be retrieved