Skip to content

docs: check upstream Kratos before implementing fork changes - #20

Merged
gn-kim-k merged 2 commits into
GoodNotes:goodnotesfrom
gn-kim-k:docs/check-upstream-before-changes
Oct 20, 2026
Merged

gn-kim-k merged 2 commits into
GoodNotes:goodnotesfrom
gn-kim-k:docs/check-upstream-before-changes

Conversation

@gn-kim-k

@gn-kim-k gn-kim-k commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

Agents working on this fork should check whether Ory Kratos already has a suitable change before implementing their own. Add root AGENTS.md as the canonical guidance and a relative CLAUDE.md -> AGENTS.md symlink so both entry points discover it.

The workflow prefers an attributed cherry-pick or minimal port, requires checking prerequisites and Goodnotes compatibility, and allows normal local implementation when no upstream change applies. PRs should record the upstream search, its outcome, and validation against this fork. Also clarify that fork PRs target goodnotes, despite the inherited upstream contribution instructions referring to master.

Upstream check

Inspected the root of ory/kratos at master commit b86338da04a040247a07f46100a86dcfb3875909; neither AGENTS.md nor CLAUDE.md exists there. This change defines Goodnotes fork maintenance policy rather than changing upstream runtime behavior.

Validation

  • Verified that CLAUDE.md resolves to AGENTS.md, reads identical contents, and is tracked by Git as a symlink (mode 120000).
  • git diff --cached --check passed.
  • Documentation only; no runtime tests needed.

This is separate from the Microsoft raw-claims fix in #19.

@gn-kim-k
gn-kim-k merged commit 43084f1 into GoodNotes:goodnotes Oct 20, 2026
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