mozilla-releng / mozilla-releng/scriptworker
Chain of Trust on Github: Migrate to the v4 API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 39
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 6
Description
We're using the v3 API, because that was the one officially supported at the time.
This led us (for instance) to use this non-API call: https://github.com/mozilla-releng/scriptworker/blob/053e76b1a0e8bbc816c5cee4a3b5e07a081f576a/scriptworker/github.py#L102-L132
That call created issues like https://github.com/mozilla-releng/scriptworker/issues/331, where we ended up manually caching the responses.
Moving to the GraphQL API may help us in removing that caching logic
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 with scriptworker/github.py lines 102-132 and the GitHub v4 migration guide linked in the issue. Review issue 331 and the existing response-caching behavior, then map the current v3 and non-API calls to GraphQL equivalents. Done means the GitHub interactions use v4 and the affected caching logic is addressed without regressing the worker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100