|
| 1 | +# Contributing to Ruby Graph Library |
| 2 | + |
| 3 | +Thank you for your interest in contributing to rgl! We welcome all |
| 4 | +contributions, whether they're big or small. Here are some guidelines to get you |
| 5 | +started. |
| 6 | + |
| 7 | +## Code of Conduct |
| 8 | + |
| 9 | +Please note that this project is released with a Contributor Code of Conduct. By |
| 10 | +participating in this project you agree to abide by its terms. |
| 11 | + |
| 12 | +## How to Contribute |
| 13 | + |
| 14 | +1. Fork the repository. |
| 15 | +2. Create a branch for your changes: `git checkout -b my-feature-branch` |
| 16 | +3. Make your changes and commit them with descriptive commit messages. |
| 17 | +4. Ensure that tests pass by running `bundle exec rake` locally. |
| 18 | +5. Push your changes to your fork: `git push origin my-feature-branch` |
| 19 | +6. Submit a pull request with your changes. |
| 20 | + |
| 21 | +## Commit Guidelines |
| 22 | + |
| 23 | +We follow the [Conventional |
| 24 | +Commits](https://www.conventionalcommits.org/en/v1.0.0/) guidelines for commit |
| 25 | +messages in this repository. Please ensure that all commit messages follow the |
| 26 | +format: |
| 27 | + |
| 28 | +``` |
| 29 | +<type>[optional scope]: <description> |
| 30 | +
|
| 31 | +[optional body] |
| 32 | +
|
| 33 | +[optional footer(s)] |
| 34 | +``` |
| 35 | + |
| 36 | +Where: |
| 37 | +- =<type>=: The type of change being made (e.g. feat, fix, docs, style, refactor, test, chore) |
| 38 | +- =<scope>= (optional): The scope of the change (e.g. component name, file name) |
| 39 | +- =<description>=: A brief description of the change |
| 40 | +- =[optional body]=: A more detailed description of the change |
| 41 | +- =[optional footer(s)]=: Any important information related to the change, such |
| 42 | + as a breaking change note |
| 43 | + |
| 44 | +By following these guidelines, it will be easier to understand the purpose of |
| 45 | +each commit and track changes over time. |
| 46 | + |
| 47 | +Please note that we may ask you to amend your commit message(s) if they do not |
| 48 | +follow these guidelines. |
| 49 | + |
| 50 | +## Issue Tracker |
| 51 | + |
| 52 | +If you find a bug or want to request a new feature, please create an issue in |
| 53 | +the GitHub issue tracker. Please provide as much detail as possible, including |
| 54 | +steps to reproduce the issue (if applicable). |
| 55 | + |
| 56 | +## Code Reviews |
| 57 | + |
| 58 | +All submissions, including submissions by project members, require review. We |
| 59 | +use GitHub pull requests for this purpose. Consult [GitHub |
| 60 | +Help](https://help.github.com/articles/about-pull-requests/) for more |
| 61 | +information on using pull requests. |
| 62 | + |
| 63 | +## License |
| 64 | + |
| 65 | +By contributing, you agree that your contributions will be licensed under the |
| 66 | +[Ruby License](../LICENSE). |
0 commit comments