Skip to content

jbud/DevOps-Coding-Challenges

View on GitHub ↗Related repositories →

active 2024-12-042024-12-12 (UTC)

Complete coverage26,446 / 26,446 hourly files (100%) · 2 absent upstream2023-08-152026-08-20 (UTC)
Events
50
Pushes
32
Pull requests
3
Issues
6
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 9 days from 2024-12-04 to 2024-12-12. Pushes: 32 total, peak 16 in a day. Pull requests: 3 total, peak 2 in a day. Issues: 6 total, peak 3 in a day. Comments: 5 total, peak 4 in a day. Stars: 0 total, peak 0 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
jbud443233
vercel[bot]2002

Recent activity

Latest issues, pull requests and releases

  • Issue#4jbud2024-12-06 09:28
    Produces extra junk in ouput from test conditions when page changed via router
  • Issue comment#4jbud2024-12-06 09:27
    Produces extra junk in ouput from test conditions when page changed via router
  • Pull request#6jbud2024-12-05 21:22
  • Issue comment#6vercel[bot]2024-12-05 21:10
    convert entire project from CRA to Vite
  • Pull request#6jbud2024-12-05 21:09
  • Issue comment#3jbud2024-12-05 04:49
    Add new Challenge via PR
  • Issue#5jbud2024-12-05 04:48
    Add types to params in Challenge type in order to properly build test.
  • Issue comment#3vercel[bot]2024-12-05 04:39
    Add new Challenge via PR
  • Issue#4jbud2024-12-05 00:00
    Produces extra junk in ouput from test conditions when page changed via router
  • Pull request#3jbud2024-12-04 22:21
  • Issue#2jbud2024-12-04 08:58
    challenge params are limited to 2 params.
  • Issue#1jbud2024-12-04 08:56
    generateTestString() causing unexpected results when executed by QuickJS
  • Issue#1jbud2024-12-04 06:17
    generateTestString() causing unexpected results when executed by QuickJS

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