How integration-intelligent/checkin works
Checkin is a small GitHub Actions-driven GLaDOS auto-check-in tool. The documented workflow supplies Cookie and User-Agent secrets, runs the script on a daily schedule, checks in each account, fetches remaining days, and optionally sends notices. The runtime implementation is concentrated in main.js; the workflow’s scheduling details are documented in the README but its source was not sampled.
Main entry points: main.js Runtime entry
Components 10
Check-in runtime
- Runtime entry
main.js - Account inputs
main.js - GLaDOS check-in
main.js - Status lookup
main.js - Notice assembly
main.js
Notifications
- Notice dispatch
main.js - Notification services
Other components
- Repository owner
- Daily Actions
- GLaDOS API
Connections 11
- Repository owner → Account inputs: sets secrets
readme.md - Daily Actions → Runtime entry: runs daily
readme.md - Runtime entry → Account inputs: reads
main.js - Account inputs → GLaDOS check-in: supplies cookies
main.js - GLaDOS check-in → GLaDOS API: posts check-in
main.js - Account inputs → Status lookup: supplies headers
main.js - Status lookup → GLaDOS API: gets account status
main.js - Runtime entry → Notice assembly: assembles outcomes
main.js - Runtime entry → Notice dispatch: calls
main.js - Notice assembly → Notice dispatch: provides messages
main.js - Notice dispatch → Notification services: sends notices
main.js