Skip to content

EESSI/eessi-bot-software-layer

View on GitHub ↗Related repositories →

Bot to help with requests to add software installations to the EESSI software layer

active 2025-04-272026-08-04 (UTC)

Partial coverage11,395 / 12,304 hourly files (93%) · 2 absent upstream · 906 failed, retryable2025-03-162026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
275
Pushes
17
Pull requests
28
Issues
31
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 465 days from 2025-04-27 to 2026-08-04. Pushes: 17 total, peak 3 in a day. Pull requests: 28 total, peak 4 in a day. Issues: 31 total, peak 9 in a day. Comments: 128 total, peak 16 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

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

ContributorContributionsPushesPRsComments
trz428761435
casparvl641434
bedroge353114
boegel326512
hound[bot]230016
Neves-P6004
sondrebr5012
laraPPr4021
ocaisa4101
github-advanced-security[bot]4004
smoors3011

Recent activity

Latest issues, pull requests and releases

  • Issue#368trz422026-03-03 09:14
    Bot is not compatible with newer Slurm versions
  • Issue comment#368bedroge2026-02-24 13:42
    Bot is not compatible with newer Slurm versions
  • Issue#368bedroge2026-02-24 12:03
    Bot is not compatible with newer Slurm versions
  • Issue comment#367bedroge2026-02-23 09:17
    `cvmfs_customizations` option is broken
  • Issue#367bedroge2026-02-20 10:11
    `cvmfs_customizations` option is broken
  • Issue comment#366Neves-P2026-02-17 10:25
    partial matches in bot instance name should not be allowed when triggering the bot
  • Issue comment#366boegel2026-02-17 09:44
    partial matches in bot instance name should not be allowed when triggering the bot
  • Pull request#361trz422026-01-28 11:59
  • Pull request#359sondrebr2026-01-28 10:31
  • Issue#360trz422026-01-27 17:29
    small improvements to bot...
  • Issue#360trz422026-01-27 17:29
    small improvements to bot...
  • Issue comment#358laraPPr2026-01-16 08:42
    The exportvariable funtionality is broken
  • Issue#186trz422026-01-06 08:50
    prevent job submission to nodes with too little local disk
  • Issue#186trz422026-01-06 08:50
    prevent job submission to nodes with too little local disk
  • Pull request#357trz422025-12-02 21:05
  • Issue comment#356casparvl2025-12-02 11:16
    Overview table from `bot:status last_build` of the bot is incomplete for large numbers of builds
  • Issue comment#356casparvl2025-12-02 11:09
    Overview table from `bot:status last_build` of the bot is incomplete for large numbers of builds
  • Issue#356casparvl2025-12-02 10:47
    Overview table from `bot:status last_build` of the bot is incomplete for large numbers of builds
  • Pull request#355trz422025-11-13 13:57
  • Pull request#352trz422025-11-12 19:15
  • Pull request#351trz422025-11-08 11:44
  • Issue#328trz422025-11-08 08:57
    Error is unclear when `app_id`, `installation_id` and/or private key aren't consistent
  • Issue#328trz422025-11-08 08:57
    Error is unclear when `app_id`, `installation_id` and/or private key aren't consistent
  • Issue#328trz422025-11-08 08:57
    Error is unclear when `app_id`, `installation_id` and/or private key aren't consistent
  • Issue#328trz422025-11-08 08:57
    Error is unclear when `app_id`, `installation_id` and/or private key aren't consistent

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.