MobileNativeFoundation / MobileNativeFoundation/XCBBuildServiceProxyKit
Pull requests should have CI run against them
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 72
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Before #15 is done, and preferably for the first PR of the rewrite, we should have CI checks running on pull requests. We can probably use BuildBuddy Workflows and GitHub actions similar to rules_xcodeproj.
Some things that we should check (and not all of it needs to be there at the start):
- Unit tests
- Linting
- Commit message check
- Documentation check
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
Review issue #15, the BuildBuddy Workflows option, and the GitHub Actions setup used by rules_xcodeproj. Define which pull-request checks are in the initial scope, then verify that CI runs for pull requests and reports the selected unit-test, lint, commit-message, and documentation checks as appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100