Skip to content

Conversation

@sjberman
Copy link
Contributor

Some fields were missing from the NGF compatibility doc, so adding those.

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

  • I have read the contributing guidelines
  • I have signed the F5 Contributor License Agreement (CLA)
  • I have rebased my branch onto main
  • I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
  • I have ensured that the commit messages adhere to Conventional Commits
  • I have ensured that documentation content adheres to the style guide
  • If the change involves potentially sensitive changes1, I have assessed the possible impact
  • If applicable, I have added tests that prove my fix is effective or that my feature works
  • I have ensured that existing tests pass after adding my changes
  • If applicable, I have updated README.md and CHANGELOG.md

Footnotes

  1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content.

Some fields were missing from the NGF compatibility doc, so adding those.
@sjberman sjberman requested a review from a team as a code owner February 20, 2025 18:23
@ADubhlaoich ADubhlaoich merged commit 0ce49b8 into nginx:main Feb 21, 2025
3 checks passed
@sjberman sjberman deleted the ngf-compat branch February 21, 2025 14:47
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.

4 participants