scrapers-us-municipal has tests! We should run these tests, as part of our code review process (opencivicdata parent repo) and deployment pattern (datamade forked repo).
From my understanding, we'll need a .travis.yml file in opencivicdata/scrapers-us-municipal that runs the tests – however, we want to keep the .travis.yml file in datamade/scrapers-us-municipal unique (i.e., it has all our deployment junk).
Is there a smart way to set this up? a way that allows us to easily fetch changes from the parent repo, without having its travis file override the DataMade one?
scrapers-us-municipalhas tests! We should run these tests, as part of our code review process (opencivicdataparent repo) and deployment pattern (datamadeforked repo).From my understanding, we'll need a .travis.yml file in
opencivicdata/scrapers-us-municipalthat runs the tests – however, we want to keep the .travis.yml file indatamade/scrapers-us-municipalunique (i.e., it has all our deployment junk).Is there a smart way to set this up? a way that allows us to easily fetch changes from the parent repo, without having its travis file override the DataMade one?