Skip to content

Added: manage-contribution-workflow skill; renamed precommit-readiness to prepush-readiness - #360

Open
mridulpathak wants to merge 2 commits into
apache:trunkfrom
mridulpathak:add-contribution-workflow-skill
Open

Added: manage-contribution-workflow skill; renamed precommit-readiness to prepush-readiness#360
mridulpathak wants to merge 2 commits into
apache:trunkfrom
mridulpathak:add-contribution-workflow-skill

Conversation

@mridulpathak

Copy link
Copy Markdown
Contributor

Adds a manage-contribution-workflow skill covering the OFBiz contribution lifecycle - fork/upstream sync, branching, optional worktree setup, the framework/plugins repo pairing, testing against real data, backporting, and PR conventions - that wasn't covered by the existing domain-pattern skills. Also corrects precommit-readiness, which mischaracterized the repository's git hook as pre-commit when it's actually pre-push (Checkstyle and CodeNarc only); renamed to prepush-readiness with accurate config paths and commands, and cross-referenced it with coding-standards.

…s to prepush-readiness

Adds a manage-contribution-workflow skill covering the OFBiz contribution lifecycle - fork/upstream sync, branching, optional worktree setup, the framework/plugins repo pairing, testing against real data, backporting, and PR conventions - that wasn't covered by the existing domain-pattern skills. Also corrects precommit-readiness, which mischaracterized the repository's git hook as pre-commit when it's actually pre-push (Checkstyle and CodeNarc only); renamed to prepush-readiness with accurate config paths and commands, and cross-referenced it with coding-standards.
… branch/PR

The skill's triggers only fired on starting or creating new work, so resuming a branch/PR from an earlier session could skip loading it entirely; and the upstream-sync step only applied at branch creation, with re-checking before a PR framed as conditional ("if time has passed"). Made both unconditional: added explicit triggers for resuming existing work and for any git push, and require an upstream fetch/drift-check before every push to an existing branch, not just the first one - this gap caused a real PR to land with a conflict.
@sonarqubecloud

sonarqubecloud Bot commented Aug 9, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant