Pull requests should have CI run against them
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
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.
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
- Dominant language
- Swift
- Stars
- 72
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from MobileNativeFoundation/XCBBuildServiceProxyKit
-
Feature Request: RewriteMay be free again @brentleyjones claimed this 1281 days ago, and no pull request is open. Open
MobileNativeFoundation/XCBBuildServiceProxyKit#15 · 8 reactions · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
MobileNativeFoundation/XCBBuildServiceProxyKit#14 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
MobileNativeFoundation/XCBBuildServiceProxyKit#9 · 1 comment ·
All issues in MobileNativeFoundation/XCBBuildServiceProxyKit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
schedule-review
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
daniezl/Hilltoppers#82 ·
Maintainers usually reply within 1 day
-
area/docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
CtcKeywordSpotter: input padding is not zeroed, so CTC log-probs are often independent of the audioOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
FluidInference/FluidAudio#991 ·
Maintainers usually reply within 1 day
-
agent-work needs-manual-intervention
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Provenance-Emu/Provenance#3726 · 4 comments ·
Maintainers usually reply within 1 day