From e4a725e67ade5c8e7c81e08304ad87af1dbce083 Mon Sep 17 00:00:00 2001 From: Martin Alfke Date: Wed, 22 Jul 2026 19:42:11 +0200 Subject: [PATCH 1/2] feat: add missing jig convert information Signed-off-by: Martin Alfke --- docs/_ecosystem_8x/devkit/migrating.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/_ecosystem_8x/devkit/migrating.md b/docs/_ecosystem_8x/devkit/migrating.md index 71ab7e4e7..f9a3527b1 100644 --- a/docs/_ecosystem_8x/devkit/migrating.md +++ b/docs/_ecosystem_8x/devkit/migrating.md @@ -11,6 +11,8 @@ When migrating away from the PDK, the biggest change you'll notice that instead Most are shipped as gems that you'll add to a module's `Gemfile`. This means that you'll maintain your own Ruby and Bundler installs, but most other tooling will be accessed via `bundle exec` commands in individual module repositories. +For simplification a convert command was added to jig starting with version 1.5.0. This allows you to automatically update your modules `Gemfile`, `Rakefile` and `spec/spec_helper.rb` to OpenVox and VoxBox compatible versions. + Before running commands in a new module repository, you'll need to run `bundle install`. If you get an error about a command not being available, you probably just need to run `bundle install`. @@ -23,12 +25,12 @@ Because Jig does not attempt to hide the Bundler environment from you, it will s {% include alert.html type="tip" title="Choosing command forms" content="If you want quick and familiar commands to run locally, then use the Jig wrapper commands. If you're running tests and such in CI or if you need to pass custom options then invoke the tools directly." %} | You used to type... | Now you type... | Or run tools directly... | -|---------------------|------------------|----------------------------------| +| ---------------------| ------------------| ----------------------------------| | `pdk new module` | `jig new module` | | | `pdk new class` | `jig new class` | | | `pdk build` | `jig build` | | | `pdk release` | `jig release` | | -| `pdk convert` | _not needed_ | | +| `pdk convert` | `jig convert` | | | `pdk update` | `jig update`* | `bundle exec msync update`* | | `pdk validate` | `jig validate` | `bundle exec rake validate lint` | | `pdk test unit` | `jig test unit` | `bundle exec rake spec` | From c514b3dc2afb790417ddbf33efa20ff540f2cc60 Mon Sep 17 00:00:00 2001 From: Martin Alfke Date: Wed, 22 Jul 2026 20:01:14 +0200 Subject: [PATCH 2/2] Add Copilot grammar and spelling suggestions Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Martin Alfke --- docs/_ecosystem_8x/devkit/migrating.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_ecosystem_8x/devkit/migrating.md b/docs/_ecosystem_8x/devkit/migrating.md index f9a3527b1..8c36d38d8 100644 --- a/docs/_ecosystem_8x/devkit/migrating.md +++ b/docs/_ecosystem_8x/devkit/migrating.md @@ -11,7 +11,7 @@ When migrating away from the PDK, the biggest change you'll notice that instead Most are shipped as gems that you'll add to a module's `Gemfile`. This means that you'll maintain your own Ruby and Bundler installs, but most other tooling will be accessed via `bundle exec` commands in individual module repositories. -For simplification a convert command was added to jig starting with version 1.5.0. This allows you to automatically update your modules `Gemfile`, `Rakefile` and `spec/spec_helper.rb` to OpenVox and VoxBox compatible versions. +For simplicity, a convert command was added to Jig starting with version 1.5.0. This allows you to automatically update your module's `Gemfile`, `Rakefile`, and `spec/spec_helper.rb` to OpenVox- and VoxBox-compatible versions. Before running commands in a new module repository, you'll need to run `bundle install`. If you get an error about a command not being available, you probably just need to run `bundle install`.