Skip to content

docs: Secure coding guide for DevSecOps stream (WIP) - #304

Draft
Gitanshi2211 wants to merge 1 commit into
mainfrom
docs/devsecops-secure-coding-guide
Draft

docs: Secure coding guide for DevSecOps stream (WIP)#304
Gitanshi2211 wants to merge 1 commit into
mainfrom
docs/devsecops-secure-coding-guide

Conversation

@Gitanshi2211

Copy link
Copy Markdown

Adding a secure coding guide for the DevSecOps stream. Starting with authentication & authorization patterns, grounded in existing auth.py and permissions.py. More sections (secrets handling, dependency management, input validation) to follow.

@github-actions

Copy link
Copy Markdown
Contributor

Preview Environment

A preview environment can be spun up on demand for this PR.

Action Label Includes
Spin up preview deploy-preview Frontend, backend, database, Redis, OPA, worker
Spin up preview with M365 deploy-preview-m365 Everything above + PowerShell service for Exchange/Teams scan testing
Tear down preview teardown-preview Stops the environment early

The environment will also be torn down automatically when the PR is closed or merged.
Preview URLs will appear in a follow-up comment once the deploy completes (~5–8 min).
M365 scans require real tenant credentials added through the frontend UI.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ffa883f5cf

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".




​```python

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Restore valid Markdown formatting in the guide

Remove the hidden character before this fence and the equivalent closing/subsequent fences: because the backticks are prefixed with U+200B, GitHub does not recognize them as fenced code blocks, so the Python examples render as ordinary, whitespace-collapsed paragraphs. The escaped heading/list markers (\###, \-) and escapes inside inline code spans likewise appear literally, leaving the new guide visibly malformed and making its examples difficult to copy correctly.

Useful? React with 👍 / 👎.

@Gitanshi2211
Gitanshi2211 marked this pull request as draft July 27, 2026 05:16
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