◆ Admin · Trade Management
Manage the trade record
—
◆ GitHub publishing settings
A fine-grained Personal Access Token is needed to commit from the browser. Scope it to this repo only with Contents: Read & write. The token is stored in localStorage on this device — it never leaves your browser.
Create a fine-grained PAT → · Repository access: EkantikCapitalAdvisors/EPIG500 only · Permissions: Contents: Read and write.
Import Discord trades
All processing happens in your browser. Drop a DiscordChatExporter HTML file, or paste raw #alerts text. Preview before staging.
▼ …or paste raw text instead
Paste Discord #alerts messages (F##: s 6940 / F##: +12.5 H3), the Ekantik journal format, a CSV row block, or a Discord JSON export. Points-based.
◆ Show supported formats
Discord #alerts (journal)
5/19/26 12.09 PM
F1: s 6940
F1: sl 6952
F1: tp 6918
F1: +12.5 H3
Prefix can be F##, M##, MO## — anything [A-Z]\w*. Side: s=short / b=long. Tag: H2=process breach / H3=variance.
Short-form (no entry block)
5/19/26 12.09 PM
F1: +12.5 H3
5/19/26 1.34 PM
F2: -8.25 H2
Just date + result. Side and entry are optional.
CSV / JSON
Native trades.json, vendor exports (Tradovate, TradeZella, IB), or a generic array of trade objects.
▼ Or add a single trade manually
Pending trades · 0 rows staged
| # | Timestamp | Symbol | Side | Result | Pts | Tag |
|---|
Apply staged trades
Output ready
Publish to repo commits the merged data/trades.json straight to main via the GitHub API — the dashboard reads it on next load (~30s after GitHub Pages redeploys). Manual download is still available as a fallback.
Manual publish (git commands)
cd EPIG500
mv ~/Downloads/trades.json data/trades.json
git add data/trades.json
git commit -m "Update trade record (N new trades)"
git push
Preview JSON
Current trade record
| # | Date | Symbol | Side | Result | Points | Tag |
|---|