Skip to content

Commit edb8abb

Browse files
authored
Remove github sections from publishing pages (covered in another page) (#373)
1 parent c78cd17 commit edb8abb

File tree

6 files changed

+5
-44
lines changed

6 files changed

+5
-44
lines changed

fern/products/sdks/overview/csharp/publishing-to-nuget.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,6 @@ you'll have a versioned package published on NuGet.
1414

1515
<Markdown src="/products/sdks/snippets/setup-fern-folder-callout.mdx"/>
1616

17-
## Set up your GitHub integration
18-
19-
1. Create a new GitHub repository called `company-csharp` (or something similar) for your SDK, if you haven't done so already.
20-
1. Install the [Fern GitHub App](https://github.com/apps/fern-api): Select **Configure**, then scroll down to **Repository Access**. Select **Only select repositories** and in the dropdown select the repository for your SDK. Click **Save**.
21-
22-
2317
## Configure `generators.yml`
2418

2519
<Steps>

fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,12 @@ you'll have a versioned package published on pkg.go.dev.
1313

1414
<Markdown src="/products/sdks/snippets/setup-fern-folder-callout.mdx"/>
1515

16-
## Set up your GitHub integration
16+
<Note>
17+
To successfully publish your SDK as a Go module, your repository must have:
18+
* **Public** visibility
19+
* An [approved license](https://pkg.go.dev/license-policy) (e.g. [MIT](https://opensource.org/license/mit), [Apache](https://www.apache.org/licenses/LICENSE-2.0))
20+
</Note>
1721

18-
1. Create a new GitHub repository called `company-go` (or something similar) for your SDK, if you haven't done so already. Make sure your repository has:
19-
* **Public** visibility
20-
* An [approved license](https://pkg.go.dev/license-policy) (e.g. [MIT](https://opensource.org/license/mit), [Apache](https://www.apache.org/licenses/LICENSE-2.0))
21-
1. Install the [Fern GitHub App](https://github.com/apps/fern-api): Select **Configure**, then scroll down to **Repository Access**. Select **Only select repositories** and in the dropdown select the repository for your SDK. Click **Save**.
2222

2323

2424
## Configure `generators.yml`

fern/products/sdks/overview/java/publishing-to-maven-central.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,6 @@ you'll have a versioned package published on Maven Central.
99

1010
<Markdown src="/products/sdks/snippets/setup-fern-folder-callout.mdx"/>
1111

12-
## Set up your GitHub integration
13-
14-
1. Create a new GitHub repository called `company-java` (or something similar) for your SDK, if you haven't done so already.
15-
1. Install the [Fern GitHub App](https://github.com/apps/fern-api): Select **Configure**, then scroll down to **Repository Access**. Select **Only select repositories** and in the dropdown select the repository for your SDK. Click **Save**.
16-
17-
1812
## Configure `generators.yml`
1913

2014
<Steps>

fern/products/sdks/overview/php/publishing-to-packagist.mdx

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -13,21 +13,6 @@ you'll have a versioned package published on Packagist.
1313

1414
<Markdown src="/products/sdks/snippets/setup-fern-folder-callout.mdx"/>
1515

16-
## Set up your GitHub integration
17-
18-
1. Create a new GitHub repository called `company-php` (or something similar) for your SDK, if you haven't done so already.
19-
<Warning>
20-
Your repository must:
21-
* Have **public** visibility. You can configure this in your repository's
22-
**Settings**.
23-
* Have a `composer.json` file in your main branch that adheres to Packagist's
24-
requirements. See Packagist's [Getting
25-
Started](https://packagist.org/) and [Naming
26-
Conventions](https://packagist.org/about#naming-your-package) documentation.
27-
</Warning>
28-
1. Install the [Fern GitHub App](https://github.com/apps/fern-api): Select **Configure**, then scroll down to **Repository Access**. Select **Only select repositories** and in the dropdown select the repository for your SDK. Click **Save**.
29-
30-
3116
## Configure `generators.yml`
3217

3318
<Steps>

fern/products/sdks/overview/python/publishing-to-pypi.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,6 @@ you'll have a versioned package published on PyPI.
1313

1414
<Markdown src="/products/sdks/snippets/setup-fern-folder-callout.mdx"/>
1515

16-
## Set up your GitHub integration
17-
18-
1. Create a new GitHub repository called `company-python` (or something similar) for your SDK, if you haven't done so already.
19-
1. Install the [Fern GitHub App](https://github.com/apps/fern-api): Select **Configure**, then scroll down to **Repository Access**. Select **Only select repositories** and in the dropdown select the repository for your SDK. Click **Save**.
20-
21-
2216
## Configure `generators.yml`
2317

2418
<Steps>

fern/products/sdks/overview/ruby/publishing-to-rubygems.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,6 @@ you'll have a versioned package published on RubyGems.
99

1010
<Markdown src="/products/sdks/snippets/setup-fern-folder-callout.mdx"/>
1111

12-
## Set up your GitHub integration
13-
14-
1. Create a new GitHub repository called `company-ruby` (or something similar) for your SDK, if you haven't done so already.
15-
1. Install the [Fern GitHub App](https://github.com/apps/fern-api): Select **Configure**, then scroll down to **Repository Access**. Select **Only select repositories** and in the dropdown select the repository for your SDK. Click **Save**.
16-
17-
1812
## Configure `generators.yml`
1913

2014
<Steps>

0 commit comments

Comments
 (0)