lvarayut/github-date-of-creation

Extension doesn't work correctly in some repositories

Open

#6 opened on Jun 1, 2019

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

Repository metrics

Stars
 (64 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I installed the extension, but I found its not working on a few repositories.

On my own (Private) repository it just displays the current month/year even though my last commit was in May.

image

And in this public repository it states October 2018 even though the repository is much older. In this particular case it seems to be referring to the date of latest commit.

Contributor guide

Research direction
Inspect the extension code to see how it retrieves the repository creation date. Verify the API endpoint used and whether it handles private repositories correctly. Also check if it incorrectly uses the latest commit date for some repositories.
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.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Mostly clear
Prerequisites
JavaScriptChrome Extension basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70