Branch: refs/heads/explicit-push-refspec Home: https://github.com/xwiki/xwiki-dev-llm Commit: c4773e03fb84a488eeec21214a076f511f9365ff https://github.com/xwiki/xwiki-dev-llm/commit/c4773e03fb84a488eeec21214a076f... Author: Thomas Mortagne <[email protected]> Date: 2026-08-19 (Wed, 19 Aug 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json M xwiki/instructions/xwiki-org.md M xwiki/okf/processes/security-policy.md M xwiki/skills/xwiki-pull-request/SKILL.md Log Message: ----------- [Misc] Always push naming the remote and the branch explicitly * Add a "Pushing" section to the org-wide instructions: `git push -u origin <branch>`, never a bare `git push`. * Explain the failure mode in the xwiki-pull-request skill, as part of the steps before opening a PR: where `push.default=matching` is configured, a bare push updates every local branch whose name also exists on the remote, so a stale local master rewinds the remote one — and `--force-with-lease` does not prevent it, because its lease only checks that the remote-tracking ref is current, which it is. The push output is the check: it must list only the intended ref. * Make the one remaining bare `git push` in the OKF explicit — the security-advisory merge recipe, where the branch pushed to is a release branch. * Bump the plugin version to 1.0.32 across all host manifests. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications