CI Visibility Terminology does not explicitly confirm Datadog terminology absent in CI provider
Maintainers usually reply within 1 day
@sasmita016 is already working on this.
Since Mar 30, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions
- Domain
- ci-cd, documentation
Research direction
Start with the GitHub Actions Terminology section and the Supported Features table, then compare the Getting Started anchor and the Pipeline Data Model guide. Check the listed CI Visibility provider pages and integrations-core proposal before editing. Done means provider terminology and unsupported terms are explicit, links work, and the relevant guide content is easy to find.
Written by the indexing model from the issue text.
Description
Documentation Page
- https://docs.datadoghq.com/getting_started/ci_visibility/?tab=pipeline#set-up-your-ci-provider
- https://docs.datadoghq.com/continuous_integration/pipelines/github/#terminology
- https://docs.datadoghq.com/continuous_integration/troubleshooting/#missing-stages-or-jobs-in-summary-tables
- https://docs.datadoghq.com/continuous_integration/pipelines/#supported-features
Issue Description
- CI Visibility Integration dashboards include a Group for Stages, which are not present in CI Provider Github Actions.
- This absence can be inferred as expected from entries in GitHub Actions Setup for CI Visibility > Terminology, but is not explicitly confirmed in the document.
- Further confusion is added in CI Visibility Troubleshooting > Missing stages or jobs in summary tables, whose link to public API endpoint specification shows Supported Features, but not a clear summary of which Providers support which Terms.
- Getting Started with CI Visibility > Set up your CI provider has a broken anchor link to a generic Terminology section.
Update
- CI Visibility Guides > Pipeline Data Model And Execution Types > Data Model does explicitly state "Some CI providers do not have this level."
Proposed Solution
- Create a separate issue against https://github.com/DataDog/integrations-core to address empty widget groups for providers where a term is absent.
- Update Terminology tables in each CI Provider document with an entry for each Datadog Term (pipeline, stage, job, step, command).
- For Terms not supported by all CI Providers, add a row to the Supported Features table, and check marks for providers that do support the term.
- Confirm or update the dead link from Getting Started with CI Visibility > Set up your CI provider now goes to this updated table.
- Make the relevant contents of Guide documentation more obvious in the main feature section by adding a link, moving or copying the contents where a user would first need to encounter it.
- Dominant language
- JavaScript
- Stars
- 621
- Forks
- 1.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 441
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DataDog/documentation
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
DataDog/documentation#39746 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
DataDog/documentation#38651 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
DataDog/documentation#37078 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DataDog/documentation#36762 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
DataDog/documentation#36300 · 1 comment ·
Maintainers usually reply within 1 day
All issues in DataDog/documentation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dusk-network/exu#17 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jspreadsheet/ce#1809 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
githubnext/gh-aw-workshop#4458 ·
Maintainers usually reply within 1 day
-
Add: CartoonitoOpencheck:failed feeds:add
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
iptv-org/database#37390 · 1 comment ·
Maintainers usually reply within 9 days
-
bug: directory index route root priority is overwritten when wildcard is falsePossibly taken @TalhaHunter101 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
fastify/fastify-static#617 ·