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?
-
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
And old code can be tested against new tests. I usually cite the example of a new vulnerability being discovered, with a test. You may like to know if the code you're maintaining has this vulnerability, but things aren't normally set up to retroactively run new tests on old code.
-
-
thank you!! it’s still difficult to thread my mind around the precise mechanics yet
-
I'm not sure I have either, at least with the "precise" qualifier. At the moment I'm just sitting with the idea, and seeing how compatible it would be with the other things I'm thinking about, and occasionally getting inspiration... "Background development" you could call it. ;)
- Show replies
New conversation -
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.