We warmly welcome contributions to the IBC Relayer Feegrant Working Group! This document provides guidelines for contributing to the relayer-feegrant-wg repository.
Before creating bug reports, please check the issue list as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible:
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as much detail as possible.
- Provide specific examples to demonstrate the steps. Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples.
- Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
- Explain which behavior you expected to see instead and why.
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main. - If you've added code that should be tested, add tests.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
This project and everyone participating in it is governed by the IBC Relayer Feegrant Working Group Code of Conduct. By participating, you are expected to uphold this code.
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project.
Can't wait to get started? Here are a couple of ways you can help:
- Check the issue tracker for open issues that interest you.
- Join the community on Discord or Telegram to discuss ideas and ask questions.
- Join our Discord or Telegram if you have any questions or want to discuss contributions in real time.
Thank you for contributing to the IBC Relayer Feegrant Working Group!