Update ios.md with limitations on "datadog-ci dsyms upload" command #31164
Conversation
Updating "iOS Crash Reporting and Error Tracking" page to reflect the limitation that the command "datadog-ci dsyms upload" only works on macOS Reference: https://github.com/DataDog/datadog-ci/tree/master/src/commands/dsyms#dsyms-command
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
There was a problem hiding this comment.
Looks great, Jeremy! I made a small edit to make it flow a little easier with the previous note.
Also, you might have noticed that some of the usual automations that happen in docs PRs haven't run for this one, and that's because your branch name doesn't have a slash in it. Usually, in this case, we'd ask you to close your PR, rename your branch to fulfill the requirements we list in the "For Datadog employees" section of the PR template and then open a new one. However, because this is such a small PR and I've been able to test it on my local build, I'll just merge it in with both of our changes this time. Just thought I'd flag it for the future!
Updating "iOS Crash Reporting and Error Tracking" page to reflect the limitation that the command "datadog-ci dsyms upload" only works on macOS
Reference: https://github.com/DataDog/datadog-ci/tree/master/src/commands/dsyms#dsyms-command
What does this PR do? What is the motivation?
To improve clarity on the "datadog-ci dsyms upload" command (only works when on macOS)
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes