-
Notifications
You must be signed in to change notification settings - Fork 105
Rename NGINX WAF and DoS #1007
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Rename NGINX WAF and DoS #1007
Conversation
✅ Deploy Preview will be available once build job completes!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot find a single internal resource describing the urgency of this change or how it relates to any timelines for the unification effort.
Changed the PR to draft. This is not due until September and will need to be reconciled closer to that date with the work I have been doing in the refactor. |
Should we create an issue ticket for the change (documenting its background and AC) vs. keeping a draft PR around for an indeterminate amount of time? |
@@ -1,6 +1,6 @@ | |||
--- | |||
# The title is the product name | |||
title: F5 NGINX App Protect DoS | |||
title: F5 F5 DoS for NGINX |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Double F5 word
should be title: F5 DoS for NGINX
Proposed changes
Rename it to comply with branding
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩