3654df4e95
Co-authored-by: Lewis Jones <ljones140@github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com> Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
1.4 KiB
title, shortTitle, allowTitleToDifferFromFilename, intro, versions, autogenerated
| title | shortTitle | allowTitleToDifferFromFilename | intro | versions | autogenerated | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| REST API endpoints for dependency submission | Dependency submission | true | Use the REST API to submit dependencies. |
|
rest |
About dependency submissions
{% data reusables.dependency-submission.about-dependency-submission %}
You can submit dependencies in the form of a snapshot. A snapshot is a set of dependencies associated with a commit SHA and other metadata, that reflects the current state of your repository for a commit. You can choose to use pre-made actions or create your own actions to submit your dependencies in the required format each time your project is built. For more information, see AUTOTITLE.
You can submit multiple sets of dependencies to be included in your dependency graph. The REST API uses the job.correlator property and the detector.name category of the snapshot to ensure the latest submissions for each workflow get shown. The correlator property itself is the primary field you will use to keep independent submissions distinct. An example correlator could be a simple combination of two variables available in actions runs: <GITHUB_WORKFLOW> <GITHUB_JOB>.
{% data reusables.dependency-graph.deduplication %}