mgedmin / mgedmin/project-summary
Use GraphQL?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Maybe I can use one GraphQL query to fetch the issue and pull request counts for all of my repos? Something like
```
query {
viewer {
pinnedRepositories(first:10) {
edges {
node {
name
issues(states:[OPEN]) {
totalCount
}
pullRequests(states:[OPEN]) {
totalCount
}
}
}
}
}
}
```
(which works today in https://developer.github.com/early-access/graphql/explorer/, only I don't want pinnedRepositories, I want to provide a list of repositories by name)
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 with the GraphQL query shown in the issue and compare it with the GitHub GraphQL Explorer behavior. Identify how a list of repositories by name should replace pinnedRepositories, and consider the request complete when issue and pull-request counts can be fetched for all specified repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100