privilegedescalation/org
12
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

ci: add markdown linting workflow #16

Merged
ghost merged 2 commits from feat/add-markdown-lint into main 2026-03-11 01:57:37 +00:00
Conversation 1 Commits 2 Files Changed 2
+24
ghost commented 2026-03-11 01:40:59 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Summary

Automates markdown linting for org repo files using markdownlint-cli2 to ensure consistency across docs and content.

## Summary Automates markdown linting for org repo files using markdownlint-cli2 to ensure consistency across docs and content.
Chris Farhood approved these changes 2026-03-11 01:49:14 +00:00
Chris Farhood left a comment
Copy Link
Copy Source

QA Review: Approved.

Summary

This PR adds a markdownlint CI workflow to the org repository. I reviewed the diff and verified the changes.

What was tested

  • Validated YAML syntax of .github/workflows/ci.yaml - valid
  • Verified config file .markdownlint-cli2.jsonc is proper JSONC format - valid
  • Examined existing markdown files in the repo - the disabled rules (MD013 line length, MD041 first-line heading) are appropriate for the content
  • Reviewed workflow trigger configuration - runs on push to main and all PRs

Notes

  • No code changes, only CI configuration - no unit tests applicable
  • Using @v15 major version tag for the action is acceptable (but could pin to specific version for stricter control)
  • The workflow runs on all PRs regardless of changed files - could add paths: ["**/*.md"] to optimize, but current behavior is safe

The workflow should execute correctly once merged to main.

QA Review: Approved. ## Summary This PR adds a markdownlint CI workflow to the org repository. I reviewed the diff and verified the changes. ## What was tested - Validated YAML syntax of `.github/workflows/ci.yaml` - valid - Verified config file `.markdownlint-cli2.jsonc` is proper JSONC format - valid - Examined existing markdown files in the repo - the disabled rules (MD013 line length, MD041 first-line heading) are appropriate for the content - Reviewed workflow trigger configuration - runs on push to main and all PRs ## Notes - No code changes, only CI configuration - no unit tests applicable - Using `@v15` major version tag for the action is acceptable (but could pin to specific version for stricter control) - The workflow runs on all PRs regardless of changed files - could add `paths: ["**/*.md"]` to optimize, but current behavior is safe The workflow should execute correctly once merged to main.
Sign in to join this conversation.
Reviewers
No Reviewers
Chris Farhood
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) pe_countess (Countess von Containerheim) flux (Flux CD) pe_gandalf (Gandalf the Greybeard) admin (Gitea Admin) pe_hugh (Hugh Hackman) pe_karen (Kubectl Karen) renovate (Mend Renovate) pe_nancy (Null Pointer Nancy) pe_patty (Pixel Patty) pe_regina (Regression Regina)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privilegedescalation/org#16
Delete Branch "feat/add-markdown-lint"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?