PR #398 introduced data/activity-state.json, which is written by scripts/analyze-inactivity.js.
The analyze-inactivity.yml workflow correctly commits only inactive-users.json. However, the sync-leaderboard.yml workflow stages changes using git add . and only resets users.json and inactive-users.json, meaning activity-state.json will also be staged and committed on every leaderboard sync and cause conflicts when both workflows run together.
Affected File
.github/workflows/sync-leaderboard.yml
Expected Behaviour
activity-state.json should only be committed by analyze-inactivity.yml. The leaderboard sync workflow should ignore it.
Proposed Fix
After the existing git reset commands in sync-leaderboard.yml, add:
git reset -q activity-state.json
PR #398 introduced
data/activity-state.json, which is written byscripts/analyze-inactivity.js.The
analyze-inactivity.ymlworkflow correctly commits onlyinactive-users.json. However, thesync-leaderboard.ymlworkflow stages changes usinggit add .and only resetsusers.jsonandinactive-users.json, meaningactivity-state.jsonwill also be staged and committed on every leaderboard sync and cause conflicts when both workflows run together.Affected File
.github/workflows/sync-leaderboard.ymlExpected Behaviour
activity-state.jsonshould only be committed byanalyze-inactivity.yml. The leaderboard sync workflow should ignore it.Proposed Fix
After the existing
git resetcommands insync-leaderboard.yml, add:git reset -q activity-state.json