maxgoedjen / maxgoedjen/xchequer
Allow different parsers
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
One for xcodebuild stock output.
One for xcpretty etc.
Maybe one for junit?
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 locating the existing parser for xcodebuild output and review how the GitHub Action reports errors and test failures. Compare the formats produced by stock xcodebuild, xcpretty, and JUnit, then define what parser selection and supported results should look like; done means each named format is handled reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100