swiftlang / swiftlang/github-workflows
Add Dependency Graph Workflow
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 115
- Forks
- 57
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Description
GitHub's dependency graph features only support parsing Package.resolved, which most libraries don't check in. In order to workaround this, GitHub offers the Dependency Submission API to allow packages to submit their own package graph. We should offer a workflow to make it easy for packages to submit this.
Essentially it just needs to run swift package resolve, parse the results and send them to the API. There's a toolkit here and examples of other languages here
Contributor 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.
Research direction
Start by reading the Dependency Submission API documentation, the dependency-submission-toolkit, and the linked examples for other languages. Determine how a GitHub Actions workflow can run swift package resolve, parse its results, and submit the package graph. Done means packages can use the workflow to publish their dependency graph without checking in Package.resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, swift
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100