Thank you for your interest in contributing to gst! We welcome bug reports, feature requests, and code contributions. This guide will help you get started.
π¦ Table of Contents
- Reporting Bugs
- Requesting Features
- Contributing Code
- Code Style
- Pull Request Process
- Community and Conduct
π Reporting Bugs
If you find a bug, please help us by reporting it:
- Search existing issues to avoid duplicates.
- Open a new issue with the following information:
- A clear and descriptive title.
- Steps to reproduce the issue.
- Expected vs.Β actual behavior.
- R version and operating system.
- Any relevant logs or screenshots.
π Submit a bug report
π‘ Requesting Features
We love hearing your ideas! To request a new feature:
- Check if the feature has already been suggested.
- Open a new issue labeled
enhancementwith:- A clear description of the feature.
- Why it would be useful.
- Any relevant examples or use cases.
π Request a feature
π§βπ» Contributing Code
We welcome contributions of all kinds β bug fixes, new functions, documentation improvements, and more.
π¨ Code Style
Please follow these conventions:
- Use tidyverse style where applicable.
- Document all exported functions using roxygen2.
- Include unit tests using testthat.
- Avoid long lines (>80 characters).
- Use meaningful commit messages.
β Pull Request Process
When submitting a PR:
- Ensure all tests pass (
devtools::test()). - Run
devtools::check()and fix any warnings or errors. - Link the PR to any related issues.
- Add a short description of your changes.
