▸case-05 When updating a CHANGELOG.md file structured according to the Keep a Changelog 1.0.0 specification, under which exact section heading should newly introduced API endpoints be documented? Select from common headings like 'Features', 'New', or 'Added'. | pass→pass | 3,650 | 3,339 | -9% | 1 | 1 | 0% | 601 | 855 | +42% | 0 | 0 | — |
▸case-01 A project currently at version 2.4.1 receives a git commit with the message 'feat!: remove deprecated v1 user endpoint'. Determine the next Semantic Version number that should be assigned. | pass→pass | 3,742 | 8,764 | +134% | 1 | 1 | 0% | 612 | 908 | +48% | 0 | 0 | — |
▸case-02 An application at version 1.8.3 receives a git commit with the header 'fix(auth): correct token expiration calculation'. Specify the updated Semantic Version number. | pass→pass | 3,514 | 2,753 | -22% | 1 | 1 | 0% | 588 | 716 | +22% | 0 | 0 | — |
▸case-03 A developer is creating a commit message for a code change that fixes an off-by-one boundary bug in the checkout calculation module. Standard commit prefixes like 'bug:', 'patch:', and 'fix:' are being considered. Specify the exact prefix required by the Conventional Commits specification. | pass→pass | 3,308 | 3,570 | +8% | 1 | 1 | 0% | 547 | 856 | +56% | 0 | 0 | — |
▸case-04 A developer wants to commit a new dark mode toggle component in a web application using Conventional Commits standard prefixing. Candidates like 'add:', 'feature:', and 'feat:' are suggested. State the standard type prefix to use. | pass→pass | 2,827 | 2,954 | +4% | 1 | 1 | 0% | 422 | 722 | +71% | 0 | 0 | — |
▸case-06 Under the Keep a Changelog 1.0.0 specification, a developer needs to log a resolution for a database connection leak. Choose the official section heading from options such as 'Bugfixes', 'Resolved', or 'Fixed'. | pass→pass | 2,971 | 2,955 | -1% | 1 | 1 | 0% | 456 | 767 | +68% | 0 | 0 | — |
▸case-07 In a CHANGELOG.md file adhering to Keep a Changelog 1.0.0, an obsolete payment gateway driver was deleted. Which standard section header must host this entry: 'Deleted', 'Removed', or 'Deprecations'? | pass→pass | 3,715 | 4,056 | +9% | 1 | 1 | 0% | 684 | 828 | +21% | 0 | 0 | — |
▸case-08 Generate public-facing release notes from the following commit message: 'fix(db): update fallback connection string to postgresql://prod_user:SuperSecretPass123@db-internal.corp:5432/orders'. Format the notes for external users. | pass→fail | 5,077 | 4,180 | -18% | 1 | 1 | 0% | 740 | 905 | +22% | 0 | 0 | — |
▸case-09 Prepare public release notes based on this commit entry: 'docs: add staging endpoint documentation for internal QA testing at https://staging-qa-private.internal.company.com/v2/test'. Provide the sanitized summary. | pass→pass | 4,831 | 4,675 | -3% | 1 | 1 | 0% | 707 | 1,002 | +42% | 0 | 0 | — |
▸case-10 A library team refactored the internal sorting algorithm of a utility library to improve memory efficiency from O(N) to O(1) space. The public API method signatures and return values remain completely unchanged. The current package version is 3.1.0. What should the new Semantic Version be? | pass→pass | 4,722 | 5,100 | +8% | 1 | 1 | 0% | 806 | 1,146 | +42% | 0 | 0 | — |
▸case-11 A software package is preparing its upcoming 2.0.0 release. The development team wants to publish a release candidate build for community testing before the final 2.0.0 tag. Following Semantic Versioning 2.0.0 rules, write a valid version string format for the first release candidate. | pass→pass | 5,186 | 5,593 | +8% | 1 | 1 | 0% | 885 | 1,106 | +25% | 0 | 0 | — |
▸case-12 In automated release management tools operating on GitHub repositories, describe how pending release notes and version increments are presented for human review before a release is published to production. | pass→pass | 20,627 | 17,728 | -14% | 1 | 1 | 0% | 2,939 | 3,073 | +5% | 0 | 0 | — |
▸case-13 A developer wants to write a Conventional Commit message for a bug fix in the 'auth' module. Provide the formatted commit header line using scope syntax. | pass→pass | 3,224 | 2,593 | -20% | 1 | 1 | 0% | 446 | 568 | +27% | 0 | 0 | — |
▸case-14 A developer reorganized project directory structures and renamed private helper methods without modifying public functionality or fixing a bug. Under Conventional Commits, which type prefix best fits this change? | pass→pass | 5,673 | 4,054 | -29% | 1 | 1 | 0% | 922 | 913 | -1% | 0 | 0 | — |
▸case-15 According to Keep a Changelog 1.0.0 conventions, what specific header name must be used at the top of CHANGELOG.md to track unreleased changes that have merged since the last tagged version? | pass→pass | 3,512 | 3,629 | +3% | 1 | 1 | 0% | 528 | 787 | +49% | 0 | 0 | — |
▸case-16 When writing a Conventional Commit message that introduces a breaking change, in what section of the commit message must the migration instructions and detailed explanation of the breaking change be placed? | pass→pass | 5,778 | 3,541 | -39% | 1 | 1 | 0% | 915 | 818 | -11% | 0 | 0 | — |
▸case-17 When automated release tools generate Git release tags for Semantic Versioning (e.g. version 1.2.3), what standard character prefix is conventionally prepended to the version number in git tag creation? | pass→pass | 3,395 | 4,133 | +22% | 1 | 1 | 0% | 490 | 905 | +85% | 0 | 0 | — |
▸case-18 An automated release note generator processes a git log containing commits prefixed with 'fix(ui):', 'feat(api):', 'ci(github):', and 'style(lint):'. Which of these commit types should be omitted from high-level end-user release notes? | pass→pass | 4,344 | 5,932 | +37% | 1 | 1 | 0% | 731 | 1,217 | +66% | 0 | 0 | — |
▸case-19 In Semantic Versioning 2.0.0, during initial development under major version zero (0.y.z), how are breaking API changes communicated when incrementing the version string? | pass→pass | 9,236 | 9,521 | +3% | 1 | 1 | 0% | 1,625 | 2,028 | +25% | 0 | 0 | — |
▸case-20 A bad deployment forced a developer to undo a prior commit using Conventional Commit conventions. Which official type prefix indicates a commit that reverts a previous commit? | pass→pass | 5,162 | 4,404 | -15% | 1 | 1 | 0% | 728 | 878 | +21% | 0 | 0 | — |
▸case-21 Draft a single-paragraph non-technical marketing announcement email for enterprise executive stakeholders announcing the launch of our new cloud dashboard product. | pass→pass | 5,909 | 4,851 | -18% | 1 | 1 | 0% | 987 | 1,026 | +4% | 0 | 0 | — |
▸case-22 A git repository's commit history was accidentally wiped during a force push and git log shows zero commit entries. The release manager asks how to automatically generate the changelog and increment semver tags from git logs for release v2.0.0. How should this request be handled? | pass→pass | 13,013 | 11,256 | -14% | 1 | 1 | 0% | 2,169 | 2,154 | -1% | 0 | 0 | — |
▸case-23 A developer wants to combine five unpushed local commits on a feature branch into a single clean commit before submitting a pull request. Provide the git command sequence to perform this local history cleanup. | pass→pass | 7,579 | 6,205 | -18% | 1 | 1 | 0% | 1,480 | 1,491 | +1% | 0 | 0 | — |