Code Contribution Guide
We would love for you to contribute to this project and help make it even better than it is today!
As a contributor, here are the guidelines we would like you to follow:
Code of Conduct
Help us keep this community open and inclusive.
Got a Question or Problem?
Do not open issues for general support questions, as we want to keep GitHub issues for bug reports and feature requests. Instead, we recommend using "Discussions" to ask support-related questions. You can also email us at email@example.com.
Found a Bug?
If you find a bug in the source code, you can help us by submitting an issue or even better, you can submit a Pull Request with a fix.
Missing a Feature?
You can request a new feature by submitting an issue to our GitHub Repository.
Individuals contributing to any of the projects will need to complete our Contributor License Agreement form.
Submitting an Issue
Before you submit an issue, please search the issue tracker. Maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.
We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, we require that you provide a minimal reproduction. Having a minimal reproducible scenario gives us a wealth of important information, without going back and forth to you with additional questions. A minimal reproduction allows us to quickly confirm a bug (or point out a coding problem), as well as confirm that we are fixing the right problem. We require a minimal reproduction to save maintainers' time, which ultimately enables them to fix more bugs. Often, developers find coding problems themselves while preparing a minimal reproduction. We understand that sometimes it might be hard to extract essential bits of code from a larger codebase, but we really need to isolate the problem before we can fix it. Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you, we will close an issue that doesn't have enough info to be reproduced. You can file new issues by selecting from our new issue templates and filling out the issue template.
Submitting a Pull Request (PR)
Before you submit your Pull Request (PR), please consider the following guidelines:
- Search GitHub for an open or closed PR that relates to your submission. You don't want to duplicate existing efforts.
- Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add. Discussing the design upfront helps to ensure that we're ready to accept your work.
- Fork the datalakehouse/datalakehouse-core repo.
- In your forked repository, make your changes in a new git branch: git checkout -b my-fix-branch main
- Create your patch, including appropriate test cases.
- Follow our Coding Rules.
- Run the full test suite, as described in the [developer documentation][dev-doc], and ensure that all tests pass.
- Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit). Adherence to these conventions is necessary because release notes are automatically generated from these messages. git commit --all NB: the optional commit -a command line option will automatically "add" and "rm" edited files.
- Push your branch to Github: git push origin my-fix-branch
- In GitHub, send a pull request to datalakehouse-core:community
Reviewing a Pull Request
The maintainers team reserves the right not to accept pull requests from community members who haven't been good citizens of the community. Such behavior includes not following the code of conduct.
Commit Message Format
This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].
We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.
Each commit message header must conform to the Commit Message Header format.
Commit Message Header
<type>: <short summary>
Must be one of the following:
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis CI, GitHub Actions, CircleCI)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- test: Adding missing tests or correcting existing tests
Use the summary field to provide a succinct description of the change:
- use the imperative, present tense: "change" not "changed" nor "changes"
- don't capitalize the first letter
- no dot (.) at the end
If you have more than one GitHub accounts, the following documents can help you sort out issues with GitHub accounts and multiple email addresses: