Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
159 lines (118 loc) · 7.29 KB

CONTRIBUTING.md

File metadata and controls

159 lines (118 loc) · 7.29 KB

Contributing Guide For Data Cloud JDBC Driver

This page lists the operational governance model of this project, as well as the recommendations and requirements for how to best contribute to Data Cloud JDBC Driver. We strive to obey these as best as possible. As always, thanks for contributing – we hope these guidelines make it easier and shed some light on our approach and processes.

Governance Model

Salesforce Sponsored

The intent and goal of open sourcing this project is to increase the contributor and user base. However, only Salesforce employees will be given admin rights and will be the final arbitrars of what contributions are accepted or not.

Issues, requests & ideas

Use GitHub Issues page to submit issues, enhancement requests and discuss ideas.

Bug Reports and Fixes

  • If you find a bug, please search for it in the Issues, and if it isn't already tracked, create a new issue. Fill out the "Bug Report" section of the issue template. Even if an Issue is closed, feel free to comment and add details, it will still be reviewed.
  • Issues that have already been identified as a bug (note: able to reproduce) will be labelled bug.
  • If you'd like to submit a fix for a bug, send a Pull Request and mention the Issue number.
  • Include tests that isolate the bug and verifies that it was fixed.

New Features

  • If you'd like to add new functionality to this project, describe the problem you want to solve in a new Issue.
  • Issues that have been identified as a feature request will be labelled enhancement.
  • If you'd like to implement the new feature, please wait for feedback from the project maintainers before spending too much time writing the code. In some cases, enhancements may not align well with the project objectives at the time.

Tests, Documentation, Miscellaneous

  • If you'd like to improve the tests, you want to make the documentation clearer, you have an alternative implementation of something that may have advantages over the way its currently done, or you have any other change, we would be happy to hear about it!
  • If its a trivial change, go ahead and send a Pull Request with the changes you have in mind.
  • If not, open an Issue to discuss the idea first.

If you're new to our project and looking for some way to make your first contribution, look for Issues labelled good first contribution.

Contribution Checklist

  • Clean, simple, well styled code
  • Commits should be atomic and messages must be descriptive. Related issues should be mentioned by Issue number.
  • Comments
    • Module-level & function-level comments.
    • Comments on complex blocks of code or algorithms (include references to sources).
  • Tests
    • The test suite, if provided, must be complete and pass
    • Increase code coverage, not versa.
    • Use any of our testkits that contains a bunch of testing facilities you would need. For example: import com.salesforce.op.test._ and borrow inspiration from existing tests.
  • Dependencies
    • Minimize number of dependencies.
    • Prefer Apache 2.0, BSD3, MIT, ISC and MPL licenses.
  • Reviews
    • Changes must be approved via peer code review

Creating a Pull Request

  1. Ensure the bug/feature was not already reported by searching on GitHub under Issues. If none exists, create a new issue so that other contributors can keep track of what you are trying to add/fix and offer suggestions (or let you know if there is already an effort in progress).
  2. Clone the forked repo to your machine.
  3. Create a new branch to contain your work (e.g. git br fix-issue-11)
  4. Commit changes to your own branch.
  5. Push your work back up to your fork. (e.g. git push fix-issue-11)
  6. Submit a Pull Request against the main branch and refer to the issue(s) you are fixing. Try not to pollute your pull request with unintended changes. Keep it simple and small.
  7. Sign the Salesforce CLA (you will be prompted to do so when submitting the Pull Request)

NOTE: Be sure to sync your fork before making a pull request.

Commit Message Format

This project uses Conventional Commits to automate versioning and release management. Please format your commit messages accordingly.

Commit Message Structure

<type>(<scope>): <subject>

<body>

<footer>
  • Type (required): The type of change (feat, fix, docs, style, refactor, perf, test, chore)
  • Scope (optional): The scope of the change (e.g., component name)
  • Subject (required): A brief description of the change
  • Body (optional): Detailed explanation of the change
  • Footer (optional): Issue references

Commit Types and Version Impact

Commit Type Version Bump Example
feat: Minor (0.41.0 → 0.42.0) feat: add connection pooling
fix: Patch (0.41.0 → 0.41.1) fix: resolve memory leak in query execution
feat!: Major (0.41.0 → 1.0.0) feat!: remove deprecated API
docs:, chore:, style:, refactor:, test: No release chore: update dependencies

Examples

feat: add support for batch query execution

fix(jdbc-core): resolve null pointer exception in metadata retrieval

feat!: remove deprecated ResultSet methods

chore: update Gradle to 8.5

Release Process

This project uses Release Please to automate releases based on conventional commits.

How Releases Work

1. Release PR Creation

When conventional commits are merged to main, Release Please automatically creates or updates a release PR that includes:

  • Version bump in gradle.properties (revision=X.Y.Z)
  • Updated CHANGELOG.md with all changes since last release
  • Updated .release-please-manifest.json

2. Release PR Review and Merge

  • The release PR is labeled with autorelease: pending
  • Team reviews the version bump and changelog
  • When merged, Release Please automatically:
    • Creates a Git tag (e.g., 0.42.0)
    • Creates a GitHub release with changelog
    • Updates version files

3. Maven Central Publishing

  • GitHub release triggers the release.yml workflow
  • Builds, tests, and publishes to Maven Central via reusable-build-publish.yml
  • Updates GitHub release with Maven Central publication status

4. Release Announcement

  • release-notifications.yml workflow announces the release

Release Workflow

1. Developer merges PR with conventional commit (e.g., "feat: add feature")
   ↓
2. Release Please creates/updates release PR
   ↓
3. Team reviews and merges release PR
   ↓
4. Release Please creates GitHub release
   ↓
5. release.yml publishes to Maven Central
   ↓
6. release-notifications.yml announces release

Code of Conduct

Please follow our Code of Conduct.

License

By contributing your code, you agree to license your contribution under the terms of our project LICENSE and to sign the Salesforce CLA