Skip to content

Actions: johanzander/bess-manager

Actions

Issue Fix

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
issue-fix.yml
974 workflow runs
974 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
fix: assert the gh api guard by behaviour, not by spelling Issue Fix #924: Issue comment #665 (comment) created by johanzander
2s
2s
fix: assert the gh api guard by behaviour, not by spelling Issue Fix #923: Issue comment #665 (comment) created by johanzander
1s
1s
fix: assert the gh api guard by behaviour, not by spelling Issue Fix #922: Issue comment #665 (comment) created by johanzander
1s
1s
fix: assert the gh api guard by behaviour, not by spelling Issue Fix #921: Issue comment #665 (comment) created by johanzander
2s
2s
Issue Fix Issue Fix #920: created by johanzander
10s
10s
Issue Fix Issue Fix #919: created by johanzander
6s
6s
fix: give the mypy gate the same environment locally and in CI Issue Fix #918: Issue comment #668 (comment) created by bess-agent
1s
1s
fix: report price health from the cache instead of re-fetching every 5 minutes Issue Fix #917: Issue comment #667 (comment) created by bess-agent
7s
7s
fix: make the mypy gate a ratchet, so it can actually be passed Issue Fix #916: Issue comment #664 (comment) created by bess-agent
1s
1s
Hysteresis: don't rewrite inverter schedule when the new plan is a near-tie with the applied one Issue Fix #915: Issue comment #485 (comment) created by Frank-Leysen
1s
1s
bug: terminal value is quantity-linear (bang-bang midnight SOE) and double-charges cycle_cost Issue Fix #914: Issue comment #602 (comment) created by Frank-Leysen
1s
1s
Accept an external consumption forecast as a time-series entity Issue Fix #913: Issue comment #428 (comment) created by Frank-Leysen
1s
1s
schedule and energy flow mismatch Issue Fix #912: Issue comment #330 (comment) created by Frank-Leysen
10s
10s
schedule and energy flow mismatch Issue Fix #911: Issue comment #330 (comment) created by Frank-Leysen
1s
1s
schedule and energy flow mismatch Issue Fix #910: Issue comment #330 (comment) created by bess-manager-claude-bot Bot
10s
10s
schedule and energy flow mismatch Issue Fix #909: Issue comment #330 (comment) created by johanzander
7s
7s
schedule and energy flow mismatch Issue Fix #908: Issue comment #330 (comment) created by Frank-Leysen
1s
1s
feat: give issues and PRs an explicit state machine, so the backlog loop can progress work Issue Fix #907: Issue comment #658 (comment) created by bess-agent
11s
11s
Battery Discharge Power sensor missing from Solax Modbus Issue Fix #906: Issue comment #542 (comment) created by dontommazo
2s
2s
Runtime error: Check grid charge state Issue Fix #905: Issue comment #643 (comment) created by bess-manager-claude-bot Bot
2s
2s
Battery Discharge Power sensor missing from Solax Modbus Issue Fix #904: Issue comment #542 (comment) created by johanzander
1s
1s
Runtime error: Check grid charge state Issue Fix #903: Issue comment #643 (comment) created by johanzander
1s
1s
feat: accept an external consumption forecast as a time-series entity Issue Fix #902: Issue comment #437 (comment) created by bess-product-owner
1s
1s
Question: How is IDLE used? Issue Fix #901: Issue comment #466 (comment) created by bess-product-owner
1s
1s
schedule and energy flow mismatch Issue Fix #900: Issue comment #330 (comment) created by Frank-Leysen
1s
1s