dominykas
commented
4 years ago Created the following repos with the following Travis setup:
- https://github.com/wiby-test/pass (one check, always passes)
- https://github.com/wiby-test/fail (one check, always fails)
- https://github.com/wiby-test/partial (two checks: one fails, one passes)
Setup:
- For now - just adding Travis - should be enough for initial testing, we may add Github Actions for completeness going forward
- We'll probably also want to add something to generate the old status checks too (there's two APIs in GH... see https://github.com/pkgjs/wiby/pull/4#discussion_r446950770)
- Locked the
masterbranch to avoid accidental commits (for one - thepassrepo head commit SHA is hardcoded inwibytests, at least for now) - It should be fine for the contributors to use that org when testing things locally, i.e. I'd imagine we don't need any other restrictions there?
I know someone mentioned this earlier at some point, but either way - I went ahead and created https://github.com/wiby-test and invited the same people who are contributors/owners here. I recommend you unsubscribe from notifications there :)
I figure a separate org is better for this, to avoid polluting pkgjs with repositories which are only used for automated tests. Don't think we need any kind of policies around these repositories - the intent is to just close everything that happens there?
I plan to next scaffold out some test repos there, which will always produce the same test results, so that we can use them to test wiby end-to-end (there's already some repos being accessed in the unit tests, but they're under @andrewhughes101's account, so I'll replace those).