Skip to content

content: update upstream documentation#8

Open
github-actions[bot] wants to merge 1 commit intomainfrom
automated/content-sync-update
Open

content: update upstream documentation#8
github-actions[bot] wants to merge 1 commit intomainfrom
automated/content-sync-update

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions bot commented Apr 6, 2026

Content Sync Summary

New Repositories

Repositories: 5 synced, 6 skipped
Files processed: 32

Unchanged files (32 across 4 repositories)

complyctl (10 files)

  • docs/CONTRIBUTING.md
  • docs/INSTALLATION.md
  • docs/PLUGIN_GUIDE.md
  • docs/QUICK_START.md
  • docs/RELEASE_PROCESS.md
  • docs/STYLE_GUIDE.md
  • docs/TESTING_FARM.md
  • docs/man/c2p-openscap-manifest.md
  • docs/man/complyctl-openscap-plugin.md
  • docs/man/complyctl.md

complyscribe (12 files)

  • docs/architecture/.trestle/author/decisions/0.0.1/template.md
  • docs/architecture/decisions/implement-cli-framework_001.md
  • docs/architecture/decisions/record-architecture-decisions_000.md
  • docs/architecture/diagrams/c4.md
  • docs/contributing.md
  • docs/troubleshooting.md
  • docs/tutorials/authoring.md
  • docs/tutorials/github.md
  • docs/tutorials/sync-cac-content.md
  • docs/tutorials/sync-oscal-content.md
  • docs/workflows/assemble_diagrams.md
  • docs/workflows/create_diagrams.md

complytime-collector-components (8 files)

  • docs/DESIGN.md
  • docs/DEVELOPMENT.md
  • docs/README.md
  • docs/attributes/README.md
  • docs/attributes/compliance.md
  • docs/attributes/policy.md
  • docs/integration/Sync_Evidence2Hyperproof.md
  • docs/publish_image/publish_image.md

gemara-content-service (2 files)

  • docs/JWT_AUTHENTICATION.md
  • docs/PUBLISH_IMAGE.md

@github-actions github-actions bot added automated documentation Improvements or additions to documentation labels Apr 6, 2026
{
"repos": {
"complyctl": "9515e3dafb25a8f4b17e61ebcc79d4a1668cd6af",
"complyctl": "33de18301a5f24af4dcbb5ac03662d4fa5769591",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@sonupreetam , do we need a PR when no docs are changed, only to update the content-lock.json? Maybe we could update these locks only when docs are also changed, in the same PR.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@marcusburghardt Thank you so much for your feedback. Currently being worked in PR #10.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Ok. So we can merge or close this. I think both options are valid. What do you prefer?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@marcusburghardt I would prefer merging it as I see a new repository being added to the lock file.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Ok. Lets do that. : )

Copy link
Copy Markdown

@marcusburghardt marcusburghardt left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants