[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-7789":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":16,"stars30d":17,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":18,"rankGlobal":9,"rankLanguage":9,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":22,"hasPages":20,"topics":23,"createdAt":9,"pushedAt":9,"updatedAt":27,"readmeContent":28,"aiSummary":29,"trendingCount":15,"starSnapshotCount":15,"syncStatus":30,"lastSyncTime":31,"discoverSource":32},7789,"xcpretty","xcpretty\u002Fxcpretty","Flexible and fast xcodebuild formatter","",null,"Ruby",4036,283,60,91,0,1,5,60.36,"Other",false,"master",true,[24,25,26],"ci","continuous-integration","ios","2026-06-12 04:00:35","![logo](http:\u002F\u002Fi.imgur.com\u002Fi2fElxx.png)\n\n__`xcpretty` is a fast and flexible formatter for `xcodebuild`__.\u003Cbr\u002F>\nIt does one thing, and it should do it well.\n\n[![Gem version](http:\u002F\u002Fimg.shields.io\u002Fgem\u002Fv\u002Fxcpretty.svg)](http:\u002F\u002Frubygems.org\u002Fgems\u002Fxcpretty)\n[![Build Status](https:\u002F\u002Ftravis-ci.org\u002Fsupermarin\u002Fxcpretty.svg?branch=master)](https:\u002F\u002Ftravis-ci.org\u002Fsupermarin\u002Fxcpretty)\n[![Code Climate](http:\u002F\u002Fimg.shields.io\u002Fcodeclimate\u002Fgithub\u002Fsupermarin\u002Fxcpretty.svg)](https:\u002F\u002Fcodeclimate.com\u002Fgithub\u002Fsupermarin\u002Fxcpretty)\n[![Reviewed by Hound](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FReviewed_by-Hound-8E64B0.svg)](https:\u002F\u002Fhoundci.com)\n\n## Installation\n``` bash\n$ gem install xcpretty\n```\n\n## Usage\n``` bash\n$ xcodebuild [flags] | xcpretty\n```\n`xcpretty` is designed to be piped with `xcodebuild` and thus keeping 100%\ncompatibility with it. It's even a bit faster than `xcodebuild` itself, since\nit saves your terminal some prints.\n\n__Important:__ If you're running `xcpretty` on a CI like Travis or Jenkins, you\nmay want to exit with same status code as `xcodebuild`.\nCI systems usually use status codes to determine if the build has failed.\n\n``` bash\n$ set -o pipefail && xcodebuild [flags] | xcpretty\n#\n# OR\n#\n$ xcodebuild [flags] | xcpretty && exit ${PIPESTATUS[0]}\n```\n\n## Raw xcodebuild output\nYou might want to use `xcpretty` together with `tee` to store the raw log in a\nfile, and get the pretty output in the terminal. This might be useful if you\nwant to inspect a failure in detail and aren't able to tell from the pretty\noutput.\n\nHere's a way of doing it:\n``` bash\n$ xcodebuild [flags] | tee xcodebuild.log | xcpretty\n```\n\n## Formats\n\n- `--simple`, `-s` (default)\n![xcpretty --simple](http:\u002F\u002Fi.imgur.com\u002FLdmozBS.gif)\n\n- `--test`, `-t` (RSpec style)\n![xcpretty alpha](http:\u002F\u002Fi.imgur.com\u002FVeTQQub.gif)\n- `--tap` ([Test Anything Protocol](http:\u002F\u002Ftestanything.org)-compatible output)\n- `--knock`, `-k` (a [simplified version](https:\u002F\u002Fgithub.com\u002Fchneukirchen\u002Fknock) of the Test Anything Protocol)\n\n## ANSI \u002F UTF-8\n\n- `--[no-]color`: Show build icons in color. (you can add it to `--simple` or `--test` format).\n  Defaults to auto-detecting color availability.\n- `--[no-]utf`: Use unicode characters in build output or only ASCII.\n  Defaults to auto-detecting the current locale.\n\n## Reporters\n\n- `--report junit`, `-r junit`: Creates a JUnit-style XML report at `build\u002Freports\u002Fjunit.xml`, compatible with Jenkins and TeamCity CI.\n\n- `--report html`, `-r html`: Creates a simple HTML report at `build\u002Freports\u002Ftests.html`.\n![xcpretty html](http:\u002F\u002Fi.imgur.com\u002F0Rnux3v.gif)\n\n- `--report json-compilation-database`, `-r json-compilation-database`: Creates a [JSON compilation database](http:\u002F\u002Fclang.llvm.org\u002Fdocs\u002FJSONCompilationDatabase.html) at `build\u002Freports\u002Fcompilation_db.json`. This is a format to replay single compilations independently of the build system.\n\nWriting a report to a custom path can be specified using `--output PATH`.\n\n## Extensions\n\n`xcpretty` supports custom formatters through the use of the\n`--formatter` flag, which takes a path to a file as an argument. The\nfile must contain a Ruby subclass of `XCPretty::Formatter`, and\nreturn that class at the end of the file. The class\ncan override the `format_*` methods to hook into output parsing\nevents.\n\n### Known extensions\n\n* [xcpretty-travis-formatter](https:\u002F\u002Fgithub.com\u002Fkattrali\u002Fxcpretty-travis-formatter): support for cleaner output in TravisCI using code folding\n\nThe recommended format is a gem containing the formatter and named\nwith an `xcpretty-` prefix, for easier discovery.\n\n\n## Team\n\n- [Marin Usalj](http:\u002F\u002Fgithub.com\u002Fsupermarin) http:\u002F\u002Fsupermar.in\n- [Delisa Mason](http:\u002F\u002Fgithub.com\u002Fkattrali) http:\u002F\u002Fdelisa.me\n","xcpretty 是一个快速且灵活的 xcodebuild 格式化工具。其核心功能包括多种输出格式（如简单、测试、TAP等），支持ANSI\u002FUTF-8颜色和字符控制，以及生成JUnit、HTML或JSON编译数据库等多种报告。技术上，通过Ruby实现，能够无缝集成到CI\u002FCD流程中，不仅保持与xcodebuild完全兼容，还能提升构建日志的可读性和解析效率。适用于iOS开发者在本地开发环境或是持续集成系统（如Travis CI, Jenkins）中使用，帮助更高效地分析Xcode项目的构建结果。",2,"2026-06-11 03:14:25","top_language"]