WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content
This repository was archived by the owner on Dec 10, 2025. It is now read-only.

Conversation

@dacharyc
Copy link
Collaborator

This PR adds two new commands to the audit-cli:

  • analyze procedures: get a breakdown of how many unique procedures exist in a file and its referenced includes, and what content selections they're tied to
  • extract procedures: create files representing each unique version of each procedure

We can use these commands to scope work and plan testing projects related to procedures. We can also potentially use the parser as a basis for future work related to procedure testing, so I've added extra documentation around the business logic for determining procedure uniqueness, reporting on them, etc.

Copy link
Collaborator

@krollins-mdb krollins-mdb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with just a couple comments. Would be good to have Cory or Caleb take a closer look.

- **Hash**: A short 6-character hash of the content (for uniqueness)

Examples:
- `before-you-begin-pull-the-mongodb-docker-image-e8eeec.rst`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For legibility, could we use underscores between the different pieces of the filename? For example:
before-you-begin_pull-the-mongodb-docker-image_e8eeec.rst

I know that's a little odd convention-wise, but it would improve scanability if we're expecting people to reference the files.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whew, this is a large file. Any way we can break it up a bit to improve maintainability?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done! 👍

Copy link
Collaborator

@cbullinger cbullinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

curious to see this in action!

// generateOutputFilename generates the output filename for a procedure.
//
// Format: {heading}-{first-step-title}-{hash}.rst
// Example: "before-you-begin-pull-the-mongodb-docker-image-a1b2c3.rst"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kind of agree with kyle that underscores would improve the readability

- Sub-procedures (ordered lists within steps)
- YAML steps files (automatically converted to RST format)

**Deterministic Parsing:**
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might be useful to link out to the PROCEDURE_PARSING doc somewhere; i found it answered a few questions that popped in my head as i was reading this README

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dacharyc dacharyc merged commit c057a78 into main Dec 5, 2025
1 check passed
@dacharyc dacharyc deleted the add-procedure-commands branch December 5, 2025 16:10
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants