From e98f7eaf48ed08446badd4e06a68b5bb81766c4f Mon Sep 17 00:00:00 2001
From: Devin <devin@cognition.ai>
Date: Thu, 20 Aug 2026 15:35:14 +0000
Subject: [PATCH 1/2] docs: note 1016 auth error in fern init step

---
 fern/products/sdks/snippets/init-fern-folder.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/fern/products/sdks/snippets/init-fern-folder.mdx b/fern/products/sdks/snippets/init-fern-folder.mdx
index 1a3799465..47cf4d3e2 100644
--- a/fern/products/sdks/snippets/init-fern-folder.mdx
+++ b/fern/products/sdks/snippets/init-fern-folder.mdx
@@ -45,7 +45,7 @@
   ```
 </Step>
 <Step title="Initialize the fern folder">
-  Initialize the fern folder with your existing OpenAPI specification. Specify your organization name using the `--organization` flag. 
+  Initialize the fern folder with your existing OpenAPI specification, in either JSON or YAML format. Specify your organization name using the `--organization` flag. 
 
   <llms-only>
   Before running `fern init`, ask the user two things:
@@ -69,10 +69,10 @@
   ```
 </CodeBlocks>
 
-  <Tip>
-    OpenAPI accepts both JSON and YAML formats.
-  </Tip>
-     
+  <Warning>
+    `fern init` can fail with a 1016 cookie error when the CLI has no authenticated session. Run [`fern login`](/learn/cli-api-reference/cli-reference/general-commands#fern-login) before `fern init`, and confirm your network doesn't block Fern's authentication endpoints.
+  </Warning>
+
   This creates a `fern` folder in your current directory.
 
   <llms-only>

From de6ff09084f43b1cc1d30f8bb78d3e834aec2d9f Mon Sep 17 00:00:00 2001
From: "fern-api[bot]" <115122769+fern-api[bot]@users.noreply.github.com>
Date: Thu, 20 Aug 2026 15:37:10 +0000
Subject: [PATCH 2/2] Lead Ruby quickstart generators.yml with GitHub output
 example

---
 .../sdks/generators/ruby/quickstart.mdx       | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/fern/products/sdks/generators/ruby/quickstart.mdx b/fern/products/sdks/generators/ruby/quickstart.mdx
index e4cdf781d..48372d9df 100644
--- a/fern/products/sdks/generators/ruby/quickstart.mdx
+++ b/fern/products/sdks/generators/ruby/quickstart.mdx
@@ -37,9 +37,19 @@ fern add fern-ruby-sdk --group {{GROUP_NAME}}
 ```
 </Template>
 
-This command adds the following `group` to `generators.yml`:
+This command adds a `group` to `generators.yml`. Set its `output` to the GitHub repository that holds your Ruby SDK, so `fern generate` opens a pull request against that repository:
 
-```yaml title="generators.yml"
+<CodeBlocks>
+```yaml title="GitHub"
+  ruby-sdk: # group name
+    generators:
+      - name: fern-ruby-sdk
+        version: <Markdown src="/snippets/version-number-ruby.mdx"/>
+        output:
+          location: github
+          repository: your-org/your-api-ruby-sdk
+```
+```yaml title="Local"
   ruby-sdk: # group name
     generators:
       - name: fern-ruby-sdk
@@ -48,6 +58,9 @@ This command adds the following `group` to `generators.yml`:
           location: local-file-system
           path: ../sdks/ruby
 ```
+</CodeBlocks>
+
+`fern add` configures the `local-file-system` output by default, which writes the SDK to a path in your working directory. Keep it while iterating locally, then switch to `github` once you have an [SDK repository](/learn/sdks/overview/project-structure) with the Fern GitHub App installed.
 </Step>
 
 <Step title="Generate the SDK">
@@ -88,4 +101,4 @@ fern generate --group ruby-sdk
 
 Follow the [Publishing to RubyGems](/learn/sdks/generators/ruby/publishing) guide to configure your gem and set up automated publishing via GitHub Actions.
 </Step>
-</Steps>
+</Steps>
\ No newline at end of file