Skip to content

Commit e7b162e

Browse files
Merge pull request #63 from djsteinmetz/contributing-bug
Fix broken link in contributing.md
2 parents 7ea30ea + 5087a3e commit e7b162e

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

CONTRIBUTING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ npm run generate-sdk
3232
4. Make your changes. Note: all of your changes should be to files in `/codegen` and not directly to any of the files in `src/` as those files get overwritten when the code is generated.
3333
5. Run `npm run build` to regenerate the sdk, compile the code, run the tests, and generate the docs
3434
6. Verify your changes work as expected. Run `npm install /path/to/this/folder` in a different project to install locally and test
35-
7. Update the [changelog](../CHANGELOG.md)
35+
7. Update the [changelog](./CHANGELOG.md)
3636
8. Commit your changes. We adhere to the [gitmoji](https://github.com/carloscuesta/gitmoji/) standard
3737
9. Update the sdk version in the [package.json](../package.json) and make a separate version commit in the format `:bookmark: v{newVersionHere}`
3838
10. Create a pull request
@@ -43,7 +43,7 @@ npm run generate-sdk
4343
Assuming you or a contributor followed the instructions for [submitting a pull request](#✨-submitting-a-pull-request) and are a maintainer you can follow these instructions to release a new version of the sdk.
4444

4545
1. Verify the version has been bumped and adheres to [semantic versioning](https://semver.org/)
46-
2. Verify the [changelog](../CHANGELOG.md) has been updated
46+
2. Verify the [changelog](./CHANGELOG.md) has been updated
4747
3. Create a publish a new release on github
4848
4. Publish on npm by running `npm run publish-please`
4949
- Defaults to pre-release. It is recommended to do a pre-release first to vet changes

0 commit comments

Comments
 (0)