Skip to content

✨ Fix issue #24: Use GitHub GraphQL API instead of REST API#179

Closed
nicokosi wants to merge 2 commits intomainfrom
issue-#24-Request-GitHub-GraphQL-API
Closed

✨ Fix issue #24: Use GitHub GraphQL API instead of REST API#179
nicokosi wants to merge 2 commits intomainfrom
issue-#24-Request-GitHub-GraphQL-API

Conversation

@nicokosi
Copy link
Copy Markdown
Owner

@nicokosi nicokosi commented Jun 23, 2025

Via Junie, using issue's description as agent prompt.
Screenshot 2025-06-23 at 08 27 06
Screenshot 2025-06-23 at 08 24 33
Screenshot 2025-06-23 at 08 24 21

nicokosi added 2 commits June 23, 2025 08:34
Via Junie, using issue's description as agent prompt.
@nicokosi
Copy link
Copy Markdown
Owner Author

It compiles, but... 😇

 RUST_LOG=pullpito=debug cargo run -- --repository nicokosi/pullpito
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.11s
     Running `target/debug/pullpito --repository nicokosi/pullpito`
[2025-06-23T15:59:48Z INFO  pullpito] Computing stats for GitHub repos '["nicokosi/pullpito"]' (with token: false)
[2025-06-23T15:59:48Z DEBUG pullpito] Query stats for GitHub repo "nicokosi/pullpito"
[2025-06-23T15:59:48Z DEBUG pullpito::github_events] No token provided for GraphQL API, which may result in rate limiting
[2025-06-23T15:59:48Z DEBUG pullpito::github_events] Content found for "nicokosi/pullpito"
[2025-06-23T15:59:48Z DEBUG pullpito::github_events] No data in GraphQL response

thread '<unnamed>' panicked at src/lib.rs:83:88:
called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "No data in GraphQL response" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@nicokosi
Copy link
Copy Markdown
Owner Author

I'll maybe try another time... or not! 😇

@nicokosi nicokosi closed this Aug 21, 2025
@nicokosi nicokosi deleted the issue-#24-Request-GitHub-GraphQL-API branch August 21, 2025 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant