feat!: migrate Dev Center CLI to TypeScript Heroku oclif plugin

.c8rc.json

@@ -0,0 +1,18 @@
+{
+  "src": ["src"],
+  "extension": [".ts"],
+  "exclude": [
+    "**/*.d.ts",
+    "**/*.test.ts",
+    "test/**/*",
+    "dist/**/*",
+    "coverage/**",
+    "**/*.mjs"
+  ],
+  "include": ["src/**/*.ts"],
+  "reporter": ["text-summary", "lcov"],
+  "statements": 80,
+  "branches": 80,
+  "functions": 80,
+  "lines": 80
+}

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,44 @@
+<!--
+When creating a PR, be sure to prepend the PR title with the Conventional Commit type (`feat`, `fix`, or `chore`). This is how we manage package versioning and generating CHANGELOG notes.
+
+Examples:
+- "feat: add growl notification to spaces:wait"
+- "fix: handle special characters in app names"
+- "chore: add dist directory to .gitignore"
+
+The expected Conventional Commit types are listed below.
+
+Learn more about [Conventional Commits](https://www.conventionalcommits.org/).
+-->
+
+## Summary
+<!-- Brief description of the changes in this PR. -->
+
+## Type of Change
+### Breaking Changes (major semver update)
+- [ ] Add a `!` after your change type to denote a change that breaks current behavior
+
+### Feature Additions (minor semver update)
+- [ ] **feat**: Introduces a new feature to the codebase
+
+### Patch Updates (patch semver update)
+- [ ] **fix**: Bug fix
+- [ ] **deps**: Dependency upgrade
+- [ ] **revert**: Revert a previous commit
+- [ ] **chore**: Change that does not affect production code
+- [ ] **refactor**: Refactoring existing code without changing behavior
+- [ ] **test**: Add/update/remove tests
+
+## Testing
+**Notes**:
+<!-- Add any context/setup necessary for testing. -->
+
+**Steps**:
+1. Replace this text with a list of steps used to validate changes or type 'Passing CI suffices'.
+2. ...
+
+## Screenshots (if applicable)
+
+## Related Issues
+GitHub issue: #[GitHub issue number]
+GUS work item: [WI number](WI link)

.github/dependabot.yml

@@ -1,11 +1,35 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-
 version: 2
 updates:
-  - package-ecosystem: "bundler"
+  - package-ecosystem: "github-actions"
     directory: "/"
+    open-pull-requests-limit: 5
     schedule:
       interval: "weekly"
+      time: "12:00"
+      day: "sunday"
+      timezone: "America/Los_Angeles"
+    commit-message:
+      prefix: "deps"
+  - package-ecosystem: "npm"
+    directory: "/"
+    open-pull-requests-limit: 5
+    schedule:
+      interval: "weekly"
+      time: "12:00"
+      day: "sunday"
+      timezone: "America/Los_Angeles"
+    commit-message:
+      prefix: "fix"
+      prefix-development: "chore"
+      include: "scope"
+    groups:
+      dev-patch-minor-dependencies:
+        dependency-type: "development"
+        update-types:
+          - "patch"
+          - "minor"
+    ignore:
+      - dependency-name: "@oclif/core"
+        update-types: ["version-update:semver-major"]
+      - dependency-name: "typescript"
+        update-types: ["version-update:semver-major"]

.github/workflows/ci.yml

@@ -0,0 +1,26 @@
+name: CI Test Suite
+
+on:
+  push:
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        node_version: ['22.x', '24.x']
+        os: [ubuntu-latest, macos-latest, windows-latest]
+      fail-fast: false
+    steps:
+      - uses: actions/checkout@v4
+      - name: Use Node.js ${{ matrix.node_version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node_version }}
+          cache: npm
+      - name: Install dependencies
+        run: npm ci
+      - name: Unit tests and lint
+        run: npm test

.github/workflows/push_dependabot_metadata.yml

@@ -0,0 +1,18 @@
+name: Send data to Security Alerts
+
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '0 16 * * *'
+
+jobs:
+  send-alerts:
+    runs-on: sfdc-hk-ubuntu-latest
+    steps:
+      - name: Send data to Security Alerts
+        uses: heroku/security-alerts-action@stable
+        with:
+          gh-app-id: ${{ secrets.SECURITY_ALERTS_GH_APP_ID }}
+          gh-app-privkey: ${{ secrets.SECURITY_ALERTS_GH_APP_PRIVKEY }}
+          webhook-url: ${{ secrets.SECURITY_ALERTS_WEBHOOK_URL }}
+          sa-token: ${{ secrets.SECURITY_ALERTS_TOKEN }}

.gitignore

@@ -1,18 +1,6 @@
-*.gem
-*.rbc
-.bundle
-.config
-.yardoc
-Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-.DS_Store
+node_modules/
+dist/
+coverage/
+*.tsbuildinfo
+.DS_Store
+oclif.manifest.json

.mocharc.json

@@ -0,0 +1,11 @@
+{
+  "require": [
+    "./test/init.mjs",
+    "tsx"
+  ],
+  "watch-extensions": ["ts"],
+  "recursive": true,
+  "reporter": "spec",
+  "timeout": 15000,
+  "node-option": ["import=tsx/esm"]
+}

CODEOWNERS

@@ -1,4 +1,9 @@
-# Comment line immediately above ownership line is reserved for related gus information. Please be careful while editing.
-* @heroku/marketing-web-ops
-* @heroku/front-end
-#ECCN:Open Source
+# All files require review from the Heroku Front-End Dev Tools team.
+
+# Comment line immediately above ownership line is reserved for related GUS information.
+# Please exercise caution while editing.
+
+#GUSINFO: Heroku FE Dev Tools,Heroku CLI & Plugins
+* @heroku/frontend-dev-tooling
+
+#ECCN:Open Source

CONTRIBUTING.md

@@ -1,14 +1,70 @@
-# Contributing to this repo
+# Contributing Guide for Dev Center CLI
 
-We welcome contributions!
+This page lists the operational governance model of this project, as well as the recommendations and requirements for how to best contribute to the Heroku Dev Center CLI plugin. 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.
 
-## Urgent Security Updates
-* If internal to Salesforce/Heroku, please contact the #marketing-web-ops team on Slack.
+# Governance Model
 
-## Any Other Contribution
+## Salesforce Sponsored
 
-* Create a topic branch from where you want to base your work (this is usually the `main` branch).
-* Make commits of logical units.
-* Check for unnecessary whitespace with `git --diff` before commiting.
-* Push your changes to a topic branch in the GitHub repository.
-* Submit a pull request to the base branch.
+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 arbiters 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](https://github.com/heroku/devcenter-cli/issues), and if it isn't already tracked,
+   [create a new issue](https://github.com/heroku/devcenter-cli/issues/new). Include steps to reproduce and expected vs actual behavior. 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](#creating_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](https://github.com/heroku/devcenter-cli/issues/new).
+-  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, `enhancement`s 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](#creating_a_pull_request) with the changes you have in mind.
+  -  If not, [open an Issue](https://github.com/heroku/devcenter-cli/issues/new) 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
+
+- [x] Clean, simple, well styled code
+- [x] Commits should be atomic and messages must be descriptive. Related issues should be mentioned by Issue number.
+- [x] Comments
+  - Module-level & function-level comments.
+  - Comments on complex blocks of code or algorithms (include references to sources).
+- [x] Tests
+  - The test suite, if provided, must be complete and pass
+  - Increase code coverage, not versa.
+- [x] Dependencies
+  - Minimize number of dependencies.
+  - Prefer Apache 2.0, BSD3, MIT, ISC and MPL licenses.
+- [x] 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).
+3. **Clone** the forked repo to your machine.
+4. **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](https://help.github.com/articles/syncing-a-fork/) before making a pull request.
+
+
+# License
+By contributing your code, you agree to license your contribution under the terms of our project [LICENSE.txt](LICENSE.txt) and to sign the [Salesforce CLA](https://cla.salesforce.com/sign-cla)