Skip to content

Add info on setting up GitHub repos and configuring GitHub Actions for npm publishing #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jul 30, 2025

Conversation

devalog
Copy link
Collaborator

@devalog devalog commented Jul 28, 2025

-Add new GitHub setup page, about structuring your repositories
-Added GitHub Actions flow to Publishing to npm guide

Copy link
Contributor

Copy link
Contributor

promptless bot commented Jul 28, 2025

✅ No documentation updates required.


Use GitHub Actions to set up a workflow that automatically publishes your new releases to npm.

To get started, navigate to the **Actions** tab in your repositiory and select **set up a workflow yourself**. GitHub will automatically set up a blank yml file in a new `.github/workflows` directory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The generator should generate the CI file when npm output and token is specified in generators.yml

For another example, see Vapi's [npm publishing GitHub Action](https://github.com/VapiAI/server-sdk-typescript/blob/main/.github/workflows/ci.yml)
</Step>

<Step title="Update `.fernignore`">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't need to .fernignore this.

Copy link
Contributor

Copy link
Contributor

@devalog devalog merged commit c711e55 into main Jul 30, 2025
1 check passed
@devalog devalog deleted the github-setup branch July 30, 2025 21:05
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.

3 participants