graphprotocol / graphprotocol/indexer
CI: Migrate unit tests to leverage local-network
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
We're often at the whim of whatever network and state we've configured for CI to use. We should look into using local-network, which would be a fresh start each time.
I have a branch there where I have added several overrides for docker compose in order to use this manifest as a development environment, perhaps this could be leveraged to build the indexer on github actions.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the GitHub Actions configuration and the unit-test setup, then inspect the linked local-network repository and its overrides-rebase branch. Determine how the local-network Docker Compose manifest could provide a fresh development environment for the indexer, with all unit tests running against it successfully in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, github-actions, typescript
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100