fix: classify acled auth diagnostics #13
Reference in New Issue
Block a user
Delete Branch "codex/issue-3-acled-diagnostics"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Addresses #3.\n\nScope:\n- support ACLED_USER/ACLED_USERNAME aliases alongside ACLED_EMAIL\n- distinguish no_credentials, auth_failed, api_failed, and live empty event sets\n- redact bearer tokens/cookies from ACLED debug output\n- add mocked regression coverage for OAuth success, auth denied, endpoint failure, and empty events\n- update ACLED source operations docs\n\nValidation:\n- git diff --check\n- no local npm/node test run per runner-only workflow; Gitea runner should execute npm run test:unit
Anpassen.
Superseded for Issue #3 by #39, which is based on the current production branch and includes the ACLED regression in
npm run test:unit.Schlie�e diesen PR als �berholt: Die ACLED-Diagnostik wurde sp�ter �ber PR #14/#39 auf dem Produktionsbranch mit Tests integriert. Diesen alten Branch mergebar zu machen w�rde �ltere ACLED-�nderungen erneut einf�hren.
Pull request closed