Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update github_community_profile table to use GraphQL API #266

Closed
graza-io opened this issue May 18, 2023 · 2 comments
Closed

Update github_community_profile table to use GraphQL API #266

graza-io opened this issue May 18, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@graza-io
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I'd like to use the GraphQL API when querying the table

Describe the solution you'd like
Update the table to use the GraphQL API

Describe alternatives you've considered
n/a

Additional context
For any fields that have paging, consider implementing that field as another table to avoid excess API calls (as per https://steampipe.io/docs/develop/plugin-release-checklist#data-ingestion).

New columns

  • None

Renamed columns

  • issue_template => issue_templates
  • pull_request_template => pull_request_templates
  • license => license_info

Removed columns

  • health_percentage
  • updated_at

Columns with data changes

  • code_of_conduct - updated json
  • contributing - updated json
  • license_info (formerly license) now has more info in updated JSON.
  • readme - updated json
  • security - updated json
@graza-io graza-io added the enhancement New feature or request label May 18, 2023
@graza-io graza-io self-assigned this May 18, 2023
@graza-io
Copy link
Contributor Author

Now on graphql-dev branch

@cbruno10
Copy link
Contributor

cbruno10 commented Jun 16, 2023

Completed in 42680ef

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants