Skip to content

expose vg describe to vg help#4947

Open
gtbil wants to merge 2 commits into
vgteam:masterfrom
gtbil:master
Open

expose vg describe to vg help#4947
gtbil wants to merge 2 commits into
vgteam:masterfrom
gtbil:master

Conversation

@gtbil

@gtbil gtbil commented Jun 29, 2026

Copy link
Copy Markdown

Changelog Entry

To be copied to the draft changelog by merger:

  • Exposes the development tool to vg describe, useful for detecting file types, through vg help

Description

Addresses a discussion in #4430 about the new vg describe subcommand.

@faithokamoto

faithokamoto commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

It's already there

https://github.com/gtbil/vg/blob/ce3c10c76aedc1584e3b09e277317f834ccd2ac3/src/subcommand/describe_main.cpp#L185

static vg::subcommand::Subcommand vg_chains("describe", "identify and describe files", vg::subcommand::WIDGET, main_describe);

(the clear copy-paste error is weird, yeah. I'm now considering adding to my option-checking script to force all the subcommand registrations to use the right names.)

But it doesn't seem to affect the output. Running vg help for me shows:

specialized graph tools:
[... other stuff ...]
  -- describe      identify and describe files

@faithokamoto

Copy link
Copy Markdown
Contributor

You could shift the PR to fix the name and update the description, though I'm not sure how much more help that would be. Otherwise I feel inclined to close this.

@faithokamoto

Copy link
Copy Markdown
Contributor

OK, I've set the unit tests to run, and once they pass this can be merged.

@faithokamoto

Copy link
Copy Markdown
Contributor

Adam showed me how to actually trigger GitLab CI tests for PRs made by non vgteam members, so that's running. Usually takes some hours, then I'll merge.

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.

2 participants