Fix DevSecOps pipeline issues#27
Open
abdulazeem-tk4vr wants to merge 1 commit into
Open
Conversation
Refactors the GitHub Actions workflow for documentation by separating the build and deploy jobs. This leverages artifacts to pass built docs and ensures more granular `contents` permissions for each job, improving pipeline robustness and security. Additionally, implements redaction of socket/session IDs in WebSocket logs. This prevents cleartext session identifiers from being exposed, enhancing overall system privacy and security. Minor code formatting adjustments are also included.
80e4c1f to
330161d
Compare
jairajdev
approved these changes
Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Redact WebSocket socket IDs before logging so session identifiers are not written to stdout/stderr. Add explicit GitHub Actions permissions with contents:read by default and a separate deploy-docs job that uses contents:write only when publishing docs to gh-pages on main.