Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pull requests should have CI run against them

Open
#16 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, testing

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MobileNativeFoundation/XCBBuildServiceProxyKit

All issues in MobileNativeFoundation/XCBBuildServiceProxyKit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.