-
-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
47 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
title: Contributing | ||
description: How to make a release in the repo | ||
--- | ||
|
||
## Local Setup | ||
|
||
- `pnpm install` | ||
- `pnpm build` | ||
|
||
### Run Local Dev build | ||
|
||
If you want to run this locally for development, you have to open two terminals and run the following commands: | ||
|
||
1. Terminal 1: `pnpm dev:core` | ||
2. Terminal 2: `pnpm dev:website` | ||
|
||
Then you can find the website under http://localhost:4321/spotlight. | ||
|
||
## Changesets | ||
|
||
Spotlight uses [Changesets](https://github.com/changesets/changesets) to track changes & versions. | ||
|
||
Whenever you make a change that is users facing, you should add a changeset to your PR. You can do this by runing the | ||
following command: | ||
|
||
```bash | ||
pnpm changeset:add | ||
``` | ||
|
||
This will guide you through the process to define the changeset. You have to select which package(s) are affected by | ||
this change, if it is a patch/minor/major change, and provide a description for the change. | ||
|
||
Note that not all PRs need a changeset (e.g. if you only write docs), and a PR can also have more than one changeset. | ||
|
||
## Publishing | ||
|
||
When you want to publish a new version, you need to trigger the | ||
[Prepare Publish](https://github.com/getsentry/spotlight/actions/workflows/prepare-publish.yml) Github Action. This | ||
action will open a PR with all versions bumped & changelogs updated according to the currently pending changesets. If | ||
you approve & merge this PR, these versions will automatically be published to NPM. |