Skip to content

Add CONTRIBUTING.md guide#1943

Merged
rugpanov merged 3 commits into
mainfrom
docs/add-contributing-guide
Jul 2, 2026
Merged

Add CONTRIBUTING.md guide#1943
rugpanov merged 3 commits into
mainfrom
docs/add-contributing-guide

Conversation

@rugpanov

@rugpanov rugpanov commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Changes

Adds a root CONTRIBUTING.md — the repository has never had one.

The guide covers:

  • Prerequisites — Node.js >=22, Yarn 3.2.x, Python
  • Getting startedyarn install and fetching the bundled Databricks CLI
  • Building and runningyarn build, the F5 Extension Development Host, and watch
  • Testing — the real test:* scripts (test:lint, test:unit, test:python, test:cov, test:integ)
  • Code styleyarn fix and the CI lint gate
  • Pull requests — the contribution flow
  • Contributor License Agreement — the manual, maintainer-driven CLA process required for Databricks-Licensed projects (no self-service form; the CLA is sent during review if a change is accepted, and must be signed before merge)

Closes #2 — the earliest open issue in the repo ("Add contribution instructions"), filed at project inception.

Tests

Docs-only change; no code paths affected. Commands, script names, and versions were cross-checked against package.json and the README. The file is prettier-formatted.

This pull request and its description were written by Isaac.

*Why*: The repo has never had contribution instructions; issue #2 (the
earliest open issue, filed at project inception) asks for a CONTRIBUTING.md
explaining how to contribute to the extension.

*What*: Add a root CONTRIBUTING.md covering prerequisites (Node/Yarn/Python),
getting started (yarn install + CLI fetch), building/running (yarn build, F5,
watch), testing (the real test:* scripts), code style (yarn fix), the pull
request flow, and the manual Contributor License Agreement process required for
Databricks-Licensed projects.

*Verification*: Commands, scripts, and versions cross-checked against
package.json and the README. Prettier-formatted. Docs-only change; no code
paths affected.

Closes #2

Co-authored-by: Isaac
@rugpanov rugpanov temporarily deployed to test-trigger-is July 1, 2026 16:58 — with GitHub Actions Inactive
Comment thread CONTRIBUTING.md
yarn workspace databricks run test:cov

# End-to-end / integration tests
yarn workspace databricks run test:integ

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Integration tests need an environment setup, specific env vars etc...
better to add separate section describing it and linking as pre-requisite on run command

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's exclude the integration tests completely, add the integration tests section with TODO as a placeholder, as you suggested. As follow-up I create a ticket to fill this placeholder.

@misha-db misha-db left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! missing instructions for e2e env setup

*Why*
PR review feedback (misha-db): integration tests need a live workspace and
specific env vars, which was not explained. `test:integ` would fail for a
contributor following the guide with no indication of what was missing.

*What*
- Add an "Integration test environment" section documenting the required env
  vars (DATABRICKS_HOST, TEST_DEFAULT_CLUSTER_ID, and PAT vs OAuth auth),
  a runnable example, the .databrickscfg profile alternative, and the
  yarn build / VSIX packaging prerequisite. Vars sourced from
  src/test/e2e/wdio.conf.ts and the sdk-extensions integ tests.
- Link the new section as a prerequisite from the test:integ command comment.

*Verification*
- npx prettier --check CONTRIBUTING.md → "All matched files use Prettier code style!"
@rugpanov rugpanov temporarily deployed to test-trigger-is July 2, 2026 14:08 — with GitHub Actions Inactive
@rugpanov rugpanov deployed to test-trigger-is July 2, 2026 14:43 — with GitHub Actions Active
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/vscode

Inputs:

  • PR number: 1943
  • Commit SHA: bafb144a08826c9b88e80dddfd696eeb84feafaa

Checks will be approved automatically on success.

@rugpanov rugpanov merged commit e9b246f into main Jul 2, 2026
8 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add contribution instructions

2 participants