Prepare MVP release readiness#98
Merged
Merged
Conversation
|
Hi @Will-thom, thank you for contributing to PR Maven CLI. I appreciate the time you spent opening this pull request. This project is intentionally shaped for focused, reviewable open source contributions, so your input helps the tool become more useful for Java and Maven teams. A maintainer will review the context, labels, and next steps as soon as possible. If this is your first contribution here, welcome aboard. Useful links:
Thank you for helping build a deterministic, local-first Maven failure triage tool. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #66 and #75.\n\nChanges:\n- Add the MVP acceptance checklist.\n- Add the v0.x release readiness checklist.\n- Update public repository/module paths to pr-cli/pr-maven-cli before v0.1.0.\n\nValidation:\n- go test ./...\n- Smoke: multi-module failure text exit 1, JSON exit 1 with findingCount 2, no-failure exit 0.