▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Bicep Cost Estimator ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Estimate Azure costs directly from Bicep and ARM templates. ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ title : Bicep Cost Estimator ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ page : https://bicepcostestimator.net/guides/contributing ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ repo : https://github.com/polatengin/washington ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ We welcome contributions to Bicep Cost Estimator! This guide explains how to set up a development environment and submit changes. Development Setup ─────────────────── > Prerequisites • .NET 10 SDK https://dotnet.microsoft.com/download • Node.js 20+ https://nodejs.org/ • GNU Make https://www.gnu.org/software/make/ • Docker https://www.docker.com/ (for website development) > Clone and Build ┌─ bash example ───────────────────────────────────────┐ │git clone https://github.com/polatengin/washington.git│ │cd washington │ │make setup-cli │ │make build-cli │ │make test-cli │ └──────────────────────────────────────────────────────┘  make setup-cli  restores the .NET dependencies for the CLI and tests. When you estimate a  .bicep  file, Bicep Cost Estimator will use a configured  bicep  binary if one is available or download the pinned version it needs automatically. If you're working on the VS Code extension or documentation website, install those dependencies explicitly: ┌─ bash example ─────────────────────────────────────┐ │make setup-extension │ │make setup-website │ └────────────────────────────────────────────────────┘ > Website Development ┌─ bash example ─────────────────────────────────────┐ │make setup-website │ │make dev-website │ └────────────────────────────────────────────────────┘ This starts the local docs stack at  http://localhost:3000  through the Express server, proxies browser traffic to Docusaurus with live reload, and serves the curl/plain-text pages. If you also want the playground API locally, build the CLI first with  make build-cli . Submitting Changes ──────────────────── 1. Fork the repository 2. Create a feature branch:  git checkout -b my-feature  3. Make your changes and add tests 4. Run  make test-cli  and, for extension changes,  make test-extension  5. Submit a pull request Project Structure ─────────────────── •  src/cli/  Description: .NET CLI application •  src/vscode-extension/  Description: VS Code extension •  src/website/  Description: Documentation website •  tests/  Description: Test projects •  docs/  Description: Documentation content (Markdown)