Skip to content

CompetetiveProgrammingPhilippines/Leetcode-Python

View on GitHub ↗Related repositories →

Solutions to Leetcode problems in Python, with clean and efficient code for easy reference and learning.

active 2025-05-042025-05-04 (UTC)

Partial coverage15,788 / 19,575 hourly files (81%) · 2 absent upstream · 3,787 failed, retryable2024-05-182026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
21
Pushes
4
Pull requests
10
Issues
1
Stars
1
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 1 days from 2025-05-04 to 2025-05-04. Pushes: 4 total, peak 4 in a day. Pull requests: 10 total, peak 10 in a day. Issues: 1 total, peak 1 in a day. Comments: 2 total, peak 2 in a day. Stars: 1 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
CompetetiveProgrammingPhilippines11451
Danncode106051

Recent activity

Latest issues, pull requests and releases

  • Issue#6CompetetiveProgrammingPhilippines2025-05-04 23:44
    Solve Leetcode Problem no. 2
  • Pull request#5CompetetiveProgrammingPhilippines2025-05-04 12:04
  • Pull request#5Danncode102025-05-04 12:04
  • Pull request#4CompetetiveProgrammingPhilippines2025-05-04 12:00
  • Pull request#4Danncode102025-05-04 12:00
  • Pull request#3CompetetiveProgrammingPhilippines2025-05-04 11:57
  • Pull request#3Danncode102025-05-04 11:57
  • Pull request#2CompetetiveProgrammingPhilippines2025-05-04 11:54
  • Issue comment#2Danncode102025-05-04 11:53
    Created Answers directory and .gitignore
  • Pull request#2Danncode102025-05-04 11:51
  • Pull request#1CompetetiveProgrammingPhilippines2025-05-04 11:47
  • Issue comment#1CompetetiveProgrammingPhilippines2025-05-04 11:47
    Created Answers directory and .gitignore
  • Pull request#1Danncode102025-05-04 11:46

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.