Skip to content

Komando4ediae/komando4Project

View on GitHub ↗Related repositories →

active 2024-02-122024-03-07 (UTC)

Complete coverage26,596 / 26,596 hourly files (100%) · 2 absent upstream2023-08-152026-08-27 (UTC)
Events
699
Pushes
126
Pull requests
94
Issues
66
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 25 days from 2024-02-12 to 2024-03-07. Pushes: 126 total, peak 23 in a day. Pull requests: 94 total, peak 18 in a day. Issues: 66 total, peak 16 in a day. Comments: 177 total, peak 31 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
JJ16700105
DaniWalkington116402914
CarlosBoulder94171026
dinho-dev89221918
VickyTinar87252410
sergiohut6522124

Recent activity

Latest issues, pull requests and releases

  • Issue#81VickyTinar2024-03-07 18:02
    Es necesario saber a que zona se refiere el modelo ClimbingCragForecast
  • Issue#83sergiohut2024-03-07 18:00
    El nombre de climbing-crag-forecast no es suficientemente descriptivo
  • Issue#85sergiohut2024-03-07 18:00
    climbing-crag-forecast aparece en dev/nivel2
  • Issue#45sergiohut2024-03-07 18:00
    Actualizar optimal-conditions.js
  • Issue#52sergiohut2024-03-07 18:00
    Relacionar pronóstico con localización y fecha
  • Issue#49sergiohut2024-03-07 18:00
    Actualizar climbing-crag-location class
  • Issue#66sergiohut2024-03-07 18:00
    Actualizar forecast.js
  • Issue#68sergiohut2024-03-07 18:00
    No hay ninguna entidad que incluya tanto los lugares de los que se van a hacer predicciones como las predicciones pasadas en esos lugares
  • Issue#69sergiohut2024-03-07 18:00
    La entidad del is.yaml localización errónea
  • Issue#70sergiohut2024-03-07 18:00
    No sabemos que hace la entidad
  • Issue#71sergiohut2024-03-07 18:00
    Duplicación de clase Forecast
  • Issue#73sergiohut2024-03-07 18:00
    Borrar archivos de milestones, personas y user histories de las ramas que partieron del nivel 2
  • Issue#79sergiohut2024-03-07 18:00
    Location no tiene export
  • Pull request#15sergiohut2024-03-07 18:00
  • Pull request#86dinho-dev2024-03-07 17:58
  • Issue comment#86sergiohut2024-03-07 17:55
    Deleted outdated file
  • Pull request#86DaniWalkington2024-03-07 17:54
  • Issue comment#15JJ2024-03-07 17:49
    [IS-23-24] level2
  • Issue#85DaniWalkington2024-03-07 17:47
    climbing-crag-forecast aparece en dev/nivel2
  • Pull request#84DaniWalkington2024-03-07 17:45
  • Issue comment#84DaniWalkington2024-03-07 17:36
    The class ClimbingCragForecast has been renamed to CountryClimbingCragForecast. Feature/#83
  • Pull request#84VickyTinar2024-03-07 17:33
  • Issue#83DaniWalkington2024-03-07 16:58
    El nombre de climbing-crag-forecast no es suficientemente descriptivo
  • Pull request#82VickyTinar2024-03-07 16:36
  • Issue#81sergiohut2024-03-07 16:15
    Es necesario saber a que zona se refiere el modelo ClimbingCragForecast

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.