When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a Code of Conduct, please follow it in all your interactions with the project.
We release new versions of this project (maintenance/features) on a monthly cadence so please be aware that some items will not get released right away.
You can contribute changes to this repo by opening a pull request:
- After forking this repository to your Git account, make the proposed changes on your forked branch.
- Go to the README.md file as it has detailed instructions on how to run the project locally and how to test the integrations.
- Commit your changes and push them to your forked repository.
- Navigate to the main
Airhornrepository and select the Pull Requests tab. - Click the New pull request button, then select the option "Compare across forks"
- Leave the base branch set to main. Set the compare branch to your forked branch, and open the pull request.
- Once your pull request is created, ensure that all checks have passed and that your branch has no conflicts with the base branch. If there are any issues, resolve these changes in your local repository, and then commit and push them to git.
- Similarly, respond to any reviewer comments or requests for changes by making edits to your local repository and pushing them to Git.
- Once the pull request has been reviewed, those with write access to the branch will be able to merge your changes into the
Airhornrepository.
If you need more information on the steps to create a pull request, you can find a detailed walkthrough in the Github documentation
To set up your development environment, you'll need the following dependencies:
- Node.js (latest)
pnpm i && pnpm testIf you are using nvm you can run the following:
nvm use && pnpm i && pnpm testThis will ensure that you are using the correct version of Node.js and install the dependencies.
To publish Airhorn to npm you first want to set the overall version in the package.json file. You can do this by updating the version field. Once you have done that then call:
pnpm version:syncPlease refer to our Code of Conduct readme for how to contribute to this open source project and work within the community.