By contributing to this project, you agree that your contributions will be licensed under the project's license (MIT OR Apache-2.0).
Thank you for your contribution!
https://github.com/Gifted-s/bd/issues
Please note that the code in v2 is the most recent (not experimental) and under active development, the src modules are for the experimental version
Fork the project and use the git clone
command to download the repository to your computer. A standard procedure for working on an issue would be to:
-
Clone the
velarixdb
repository and download it to your computer.git clone https://github.com/Gifted-s/velarixdb
-
Pull all changes from the upstream
main
branch, before creating a new branch - to ensure that yourmain
branch is up-to-date with the latest changes:git pull
-
Create a new branch from
main
like:bugfix-232-ensure-compaction-runs-within-time-frame-allocated
:git checkout -b "[the name of your branch]"
-
Make changes to the code, and ensure all code changes are formatted correctly:
cargo fmt
-
Ensure all clippy rules are obeyed:
cargo clippy --tests
-
Ensure nothing is unexpectedly broken:
cargo test
-
Commit your changes when finished:
git add -A git commit -m "[your commit message]"
-
Push changes to GitHub:
git push origin "[the name of your branch]"
-
Submit your changes for review, by going to your repository on GitHub and clicking the
Compare & pull request
button. -
Ensure that you have entered a commit message which details the changes, and what the pull request is for.
-
Now submit the pull request by clicking the
Create pull request
button. -
Wait for code review and approval.
-
After approval, your pull request will be merged.