https://github.com/foundry-rs/hardhat

Foundry-Hardhat plugins: Use Foundry for Hardhat projects
https://github.com/foundry-rs/hardhat

anvil ethereum forge foundry hardhat

Last synced: 2 months ago
JSON representation

Foundry-Hardhat plugins: Use Foundry for Hardhat projects

• Host: GitHub
• URL: https://github.com/foundry-rs/hardhat
• Owner: foundry-rs
• License: other
• Created: 2022-05-05T14:43:37.000Z (about 2 years ago)
• Default Branch: develop
• Last Pushed: 2023-10-03T18:44:55.000Z (9 months ago)
• Last Synced: 2024-03-23T16:46:56.223Z (3 months ago)
• Topics: anvil, ethereum, forge, foundry, hardhat
• Language: TypeScript
• Homepage:
• Size: 611 KB
• Stars: 88
• Watchers: 6
• Forks: 17
• Open Issues: 10
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Lists

• awesome-foundry - Foundry Hardhat - Hardhat plugins to use foundry tools in hardhat environments. (Tools)

README

        
---

This repo contains [hardhat](https://github.com/NomicFoundation/hardhat) plugins to use [foundry](https://github.com/foundry-rs/foundry/) tools in hardhat environments.

## Installation

See in each plugin

- [anvil](./packages/hardhat-anvil/README.md)

- [forge](./packages/hardhat-forge/README.md)

- [foundryup](./packages/easy-foundryup/README.md)

## Documentation

- [Foundry repo](https://github.com/foundry-rs/foundry/)

- [Foundry book](https://book.getfoundry.sh/)

- [Anvil](https://github.com/foundry-rs/foundry/tree/master/anvil)

## Releases

### The develop branch

_Adapted from Optimism's [release process](https://github.com/ethereum-optimism/optimism#overview)_

Our primary development branch is [`develop`](https://github.com/foundry-rs/hardhat/tree/develop/).

Developers can release new versions of the software by adding changesets to their pull requests using `yarn changeset`. Changesets will persist over time on the `develop` branch without triggering new version bumps to be proposed by the Changesets bot. Once changesets are merged into `master`, the bot will create a new pull request called "Version Packages" which bumps the versions of packages. The correct flow for triggering releases is to update the base branch of these pull requests onto `develop` and merge them, and then create a new pull request to merge `develop` into `master`. Then, the `release` workflow will trigger the actual publishing to `npm` and Docker hub.

Be sure to not merge other pull requests into `develop` if partially through the release process. This can cause problems with Changesets doing releases and will require manual intervention to fix it.

## Contributing

See [contributing guidelines](https://github.com/foundry-rs/foundry/blob/master/CONTRIBUTING.md)