Skip to content

docs: sync fork dev and refresh Learn page statistics - #324

Open
parthrohit22 wants to merge 1 commit into
openshield-org:devfrom
parthrohit22:dev
Open

docs: sync fork dev and refresh Learn page statistics#324
parthrohit22 wants to merge 1 commit into
openshield-org:devfrom
parthrohit22:dev

Conversation

@parthrohit22

@parthrohit22 parthrohit22 commented Aug 29, 2026

Copy link
Copy Markdown
Member

Summary

Synchronizes parthrohit22/openshield:dev with the current openshield-org/openshield:dev and retains the regenerated Learn page and README statistics.

Why this PR exists

The hosted Learn page was connected to my fork rather than the upstream repository. As a result, changes merged into openshield-org/openshield did not appear on that deployment.

I synchronized the fork's dev branch with upstream to reconcile the divergence. Documentation conflicts were resolved against the current upstream dev state, and the statistics refresh produced the final values in this PR.

A separate hosting configuration update is needed to connect the deployment to openshield-org/openshield so future upstream merges deploy directly.

Changes

  • Updates documentation statistics to 96 Azure security rules and 96 remediation playbooks.
  • Updates the Learn page's Compute count to 5 and MEDIUM-severity count to 32.
  • Documentation-only change; no scanner, API, infrastructure, credential, governance, or policy-document changes.

Validation

  • PR is mergeable with no unresolved conflicts.
  • Branch history contains one DCO-signed commit.
  • OpenShield CI, DCO, CodeQL, and Dependency Review all pass.

Synchronize the fork with upstream dev and refresh derived Learn page and README statistics.

Signed-off-by: Parth Rohit <parthrohit60@gmail.com>
@parthrohit22 parthrohit22 changed the title Dev docs: sync fork dev and refresh Learn page statistics Aug 29, 2026
@parthrohit22 parthrohit22 self-assigned this Aug 29, 2026
@parthrohit22
parthrohit22 requested a review from m-khan-97 August 29, 2026 12:36
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.

1 participant