Skip to content

Add CONTRIBUTING.md guide#1943

Open
rugpanov wants to merge 1 commit into
mainfrom
docs/add-contributing-guide
Open

Add CONTRIBUTING.md guide#1943
rugpanov wants to merge 1 commit 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
@github-actions

github-actions Bot commented Jul 1, 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: 65fea86176df4228b0221529d5d04829931e3a24

Checks will be approved automatically on success.

@rugpanov rugpanov temporarily deployed to test-trigger-is July 1, 2026 16:58 — with GitHub Actions Inactive
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

1 participant