lvarayut/github-date-of-creation

Use Authenticated Requests to relax rate limiting

Open

#1 opened on Aug 6, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (7 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (65 stars)
PR merge metrics
 (PR metrics pending)

Description

The date is being displayed as August 2017 (the current data) due to rate-limiting for me.

The reason: a request to api.github.com/repos/graphql/graphql-js returns a 403 response:

{
  "message": "API rate limit exceeded for xx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
  "documentation_url": "https://developer.github.com/v3/#rate-limiting"
}

I also have Notifier for GitHub installed, which is probably part of the problem, as the extensions would share a rate limit.

Contributor guide

Research direction
Modify the GitHub API request to include authentication (e.g., Authorization header with a personal access token) to avoid rate limiting.
Tech stack
javascript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitChrome extension development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80