-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Rename organization to Datadog? #8028
Comments
Hi @RohanTalip - thanks for pointing this out! It's a fair point, but we have internal processes that depend on the incorrect |
Merged
6 tasks
knksmith57
added a commit
to knksmith57/argo-rollouts
that referenced
this issue
May 24, 2023
See DataDog/documentation#8028 for more context. Signed-off-by: Kyle Smith <[email protected]>
zachaller
pushed a commit
to argoproj/argo-rollouts
that referenced
this issue
May 24, 2023
…2809) See DataDog/documentation#8028 for more context. Signed-off-by: Kyle Smith <[email protected]>
ParjadM
pushed a commit
to ParjadM/ArgoRollOut
that referenced
this issue
Dec 8, 2024
…(#2809) See DataDog/documentation#8028 for more context. Signed-off-by: Kyle Smith <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
(There doesn't really seem like a good place to file this; this repository seemed like the best choice.)
Should the "DataDog" GitHub organization be renamed to "Datadog" (note the lowercase second "d") to be consistent with the branding of the Datadog company, or even all lowercase like https://github.com/google and https://github.com/microsoft
It looks like Datadog was using that form ("Datadog", only first letter capitalized) as early as 2010: https://web.archive.org/web/20100809050504/http://www.datadoghq.com/
It seems like GitHub doesn't care about case in URLs, e.g. https://github.com/Datadog and https://github.com/datadog are the same organization as https://github.com/DataDog, so I don't think you would have to worry about links breaking.
The text was updated successfully, but these errors were encountered: