Skip to content

[fern-replay] Initialize Replay for SDK customizations#833

Open
fern-api[bot] wants to merge 1 commit intomasterfrom
fern-replay/init-1777398108152-1805a0ed
Open

[fern-replay] Initialize Replay for SDK customizations#833
fern-api[bot] wants to merge 1 commit intomasterfrom
fern-replay/init-1777398108152-1805a0ed

Conversation

@fern-api
Copy link
Copy Markdown
Contributor

@fern-api fern-api Bot commented Apr 28, 2026

Replay Initialization

This PR initializes Fern Replay for this SDK repository.
Replay automatically preserves your customizations across SDK regenerations.

Base generation commit: ae22120

Clean start — no historical patches imported. Future customizations will be tracked automatically.


Once merged, your customizations will be automatically preserved on future fern generate runs.

@fern-api fern-api Bot requested a review from a team as a code owner April 28, 2026 17:41
fern-support pushed a commit to fern-api/fern that referenced this pull request Apr 28, 2026
…le (#15504)

`replayInit()` writes `.gitattributes` into a temp clone that is then
discarded — the actual PR is built server-side by Fiddle, but the wire
body never carried the entries, so generated PRs were missing the
`linguist-generated=true` marker (e.g. auth0/auth0-python#833).

Adds a `gitattributesEntries` field to `ReplayInitResult` and the
Fiddle submit body (both v1 inline and v2 `submitReplayInit`). Drops
the unused `replayYmlContent` field and the temp-clone writes that
went nowhere. Requires a matching Fiddle change to consume the new
field; until that lands the field is silently ignored (no regression).
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.

0 participants