react-native-webrtc / react-native-webrtc/react-native-callkeep
CI for stability and PR verification
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
We closed the bug ticket that originated this conversation, but I really think this is something we should get started on. As owners, I think @manuquentin or @sboily needs to set up the initial link with Travis (they provide tremendous resources for OSS projects and are the clear choice to me, but that can be discussed here too). Once the initial setup is in place, probably just verifying building the example project, we can start discussing what kind of test setup we want and what coverage to require on PRs, etc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Travis integration and the example project build, then identify how pull requests could trigger verification. Done would include an agreed CI setup that builds the example project and a decided approach for PR tests and coverage requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- build-system, ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100