Skip to content

pull_request_template.md

Latest commit

 

History

History
36 lines (28 loc) · 1.95 KB

pull_request_template.md

File metadata and controls

36 lines (28 loc) · 1.95 KB

Summary

  • Short summary of the change and the exact section(s) modified (e.g., “Updated Section 3.1.6: Key Usage wording”).

Rationale

  • One or two sentences explaining why the change is required (policy update, audit alignment, editorial fix, etc.).

Changes

  • Bullet list of files modified (e.g., Requirements.md: Section 3.1.6 updated).

References

  • Links to authoritative sources (CABForum, WebTrust/ETSI, CCADB, aka.ms links).

Changelog entry

  • Proposed Changelog.md line (version | YYYY-MM-DD | Short summary): | 1.x | YYYY-MM-DD | Short summary: "..." |

Program reviewers & sign-off

  • If this change affects audit, trust, or program behavior, @msroot@microsoft.com must be added as a reviewer and explicit sign-off requested.

Compliance checklist (audit-related PRs)

  • Does this change affect Audit Requirements? If yes, indicate which standard applies: WebTrust / ETSI / Equivalent.
  • Have you included proposed attestation wording or the text required for auditors?
  • Have you documented any CCADB actions required (upload, attestation metadata) and who will perform them?
  • Have you added timelines for auditor/CCADB contact and expected completion dates?
  • Did you add msroot@microsoft.com as a reviewer and request explicit Program sign-off?
  • Opened an Audit submission issue using .github/ISSUE_TEMPLATE/audit-submission.md and linked it here (issue #...)

Checklist

  • Updated Requirements.md with the final wording and section number(s)
  • Added or updated Changelog.md with version, date, and short summary
  • Provided a short rationale and authoritative reference link(s) in the PR body
  • Marked Program-team reviewers and requested msroot@microsoft.com sign-off if policy- or audit-affecting
  • Verified Markdown renders correctly (preview) and tables align

Tip: Use PR titles following the pattern REQ:, ADD:, or CHG: (e.g., REQ: Update Section 3.1.6 Key Usage wording).