Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity
Files
3ea057794c637ab62681353a47908ce7ba143875
holocron/plugins/git/.apm/skills/git-branches/references/sources.md
Defame1297 740f631d1d docs(provenance): migrate the corpus to the Research registry grammar 
Repoint every `Research doc:` at the plugin's Research registry
(git/sources.md, pre-commit/sources.md, gitea/sources.md,
agentsmd/sources.md), keeping the old topic-doc link as a parenthetical
`(digest: ...)` annotation. Brace expansions and the gitea-releases
semicolon pair collapse to one path.

Entries with no registry (org-commit-conventions, org-git-conventions,
governance-secrets-hard-prohibition, adr-0002-0003-two-tier-claude-md)
now declare `none` plus `Basis:` bullets. The two git entries cite
core/instructions/git.md and commits.md as `(removed in 5deed07)`.

Remove the house-vale-3-15-2-repro entry and its source_keys citations
from vale-config and vale-run. It claimed six behaviours were reproduced
against purpose-built fixtures in this repo, but the entry was added in
d1afdbe with no test or fixture files, and none exists in history. The
behavioural rules stay; only the unbacked provenance claim goes.

Refs: #121
ADR: 0028
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EGHFJextYtVQseaHPDDhxB
2026-09-21 17:28:21 +00:00

2.6 KiB
Raw Blame History

nvie-gitflow-post

Description: Original 2010 post by Vincent Driessen introducing the Gitflow branching model, including a 2020 reflection note recommending GitHub Flow for continuous delivery teams.

Source: https://nvie.com/posts/a-successful-git-branching-model/

  • Research doc: plugins/git/docs/research/docs/git/sources.md (digest: plugins/git/docs/research/docs/git/gitflow.md — whole-document reference)

Contributing files:

  • SKILL.md (Gitflow vs. GitHub Flow inference and the not-mixable rule)
  • references/branch-patterns.md (Gitflow vs. GitHub Flow structure, defaults, and why the two are not mixable)

atlassian-gitflow-tutorial

Description: Atlassian's comprehensive Gitflow tutorial covering all five branch types, lifecycle steps, and CLI usage.

Source: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow

  • Research doc: plugins/git/docs/research/docs/git/sources.md (digest: plugins/git/docs/research/docs/git/gitflow.md — whole-document reference)

Contributing files:

  • SKILL.md (Gitflow vs. GitHub Flow inference and the not-mixable rule)
  • references/branch-patterns.md (Gitflow branch types, base/merge targets, --no-ff requirement)
  • references/merging.md (--no-ff requirement on Gitflow supporting-branch merges)

gitflow-cheatsheet

Description: Visual cheatsheet for the git-flow CLI commands (git-flow-avh fork), covering all subcommands for feature, release, and hotfix branches.

Source: https://danielkummer.github.io/git-flow-cheatsheet/

  • Research doc: plugins/git/docs/research/docs/git/sources.md (digest: plugins/git/docs/research/docs/git/gitflow.md — whole-document reference)

Contributing files:

  • references/branch-patterns.md (feature/release/hotfix naming conventions)

context7-git-htmldocs

Description: Official Git HTML documentation from the git/htmldocs repository — covers all commands, concepts, and internals.

Source: context7:/git/htmldocs

  • Research doc: plugins/git/docs/research/docs/git/sources.md (digest: plugins/git/docs/research/docs/git/branching-merging.md — whole-document reference)

Contributing files:

  • SKILL.md (Gotchas — git switch abort-on-conflict behaviour, branch/tag name ambiguity)
  • references/branch-operations.md (git switch/git branch command vocabulary and flags)
  • references/merging.md (git merge strategies and conflict-resolution commands)
  • references/comparing-branches.md (git log/git diff/git merge-base range syntax)
Reference in New Issue View Git Blame Copy Permalink