Skip to content

Latest commit

 

History

History
161 lines (100 loc) · 6.03 KB

CONTRIBUTING.md

File metadata and controls

161 lines (100 loc) · 6.03 KB
Raw

Contributing

Thanks for your interest in contributing to Hopfield! Please take a moment to review this document before submitting a pull request.

If you want to contribute, but aren't sure where to start, you can create a new discussion.

Note Please ask first before starting work on any significant new features.

It's never a fun experience to have your pull request declined after investing time and effort into a new feature. To avoid this from happening, we request that contributors create a feature request to first discuss any API changes or significant new ideas.


Basic guide

This guide is intended to help you get started with contributing. By following these steps, you will understand the development process and workflow.

  1. Cloning the repository
  2. Installing Node.js and Bun
  3. Installing dependencies
  4. Running tests
  5. Writing documentation
  6. Submitting a pull request

Advanced guide

This guide covers more advanced topics. Pick the topics based on your needs.

  1. Versioning


Cloning the repository

To start contributing to the project, clone it to your local machine using git:

git clone https:/EnjoinHQ/hopfield.git

Or the GitHub CLI:

gh repo clone EnjoinHQ/hopfield

Installing Node.js and Bun

wagmi uses Bun workspaces to manage multiple projects. You need to install Node.js v18 or higher and Bun v1 or higher.

You can run the following commands in your terminal to check your local Node.js and Bun versions:

node -v
bun -v

If the versions are not correct or you don't have Node.js or Bun installed, download and follow their setup instructions:

Installing dependencies

Once in the project's root directory, run the following command to install the project's dependencies:

bun install

After the install completes, Bun links packages across the project for development and git hooks are set up.

Running tests

Tests are run with bun test:

bun run test

Writing documentation

Documentation lives in the docs directory and in code using TSDoc. If you think something is unclear or could be explained better, you are welcome to open a pull request. To run the docs site, run the following command:

bun run docs:dev

Submitting a pull request

When you're ready to submit a pull request, you can follow these naming conventions:

  • Pull request titles use the Imperative Mood (e.g., Add something, Fix something).
  • Changesets use past tense verbs (e.g., Added something, Fixed something).

When you submit a pull request, GitHub will automatically lint, build, and test your changes. If you see an ❌, it's most likely a bug in your code. Please, inspect the logs through the GitHub UI to find the cause.


✅ Now you're ready to contribute to Hopfield! Follow the next steps if you need more advanced instructions.

Versioning

When adding new features or fixing bugs, we'll need to bump the package versions. We use Changesets to do this.

Note Only changes to the codebase that affect the public API or existing behavior (e.g. bugs) need changesets.

Each changeset defines which package(s) should be published and whether the change should be a major/minor/patch release, as well as providing release notes that will be added to the changelog upon release.

To create a new changeset, run bun run changeset. This will run the Changesets CLI, prompting you for details about the change. You’ll be able to edit the file after it’s created — don’t worry about getting everything perfect up front.

Even though you can technically use any markdown formatting you like, headings should be avoided since each changeset will ultimately be nested within a bullet list. Instead, bold text should be used as section headings.

If your PR is making changes to an area that already has a changeset (e.g. there’s an existing changeset covering theme API changes but you’re making further changes to the same API), you should update the existing changeset in your PR rather than creating a new one.

Releasing

The first time a PR with a changeset is merged after a release, a new PR will automatically be created called chore: version packages. Any subsequent PRs with changesets will automatically update this existing version packages PR. Merging this PR triggers the release process by publishing to npm and cleaning up the changeset files.

Creating a snapshot release

If a PR has changesets, you can create a snapshot release by manually dispatching the Snapshot workflow. This publishes a tagged version to npm with the PR branch name and timestamp.