graphprotocol / graphprotocol/graph-node
[Feature] Include pointer to source in subgraph manifest
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Description
Most subgraphs are maintained in git, but once they are deployed, the connection to the source is lost. Subgraph schemas should make it possible to include a URL to a git repo and a commit hash to make it possible to trace the provenance of a deployed subgraph. This should be supported by graph-cli to make filling these fields convenient, and probably needs some option to turn it off for people who do not want that information published.
Some information to help us out
- Tick this box if you plan on implementing this feature yourself.
- I have searched the issue tracker to make sure this issue is not a duplicate.
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 tracing how subgraph schemas and manifests are represented and how graph-cli currently fills deployment metadata. Define how a git repository URL and commit hash would be stored, how graph-cli would populate them, and how users could disable publication; the feature is done when deployed subgraphs preserve this provenance without requiring it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, graphql, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100