Skip to content

fix: require complete weekly traffic data - #233

Merged
DanWahlin merged 1 commit into
mainfrom
fix/traffic-complete-week
Sep 29, 2026
Merged

DanWahlin merged 1 commit into
mainfrom
fix/traffic-complete-week

Conversation

@DanWahlin

Copy link
Copy Markdown
Collaborator

Summary

  • require exactly seven consecutive, complete traffic dates
  • no-op when the GitHub traffic API is delayed or missing dates
  • verify both CSV files receive the same seven-day window

This prevents partial-week updates like #232. That PR should be closed without merging and retried after the API reports the complete September 21–27 window.

Validation

  • gh aw compile traffic-updater --no-emit --validate --no-check-update

Wait for all seven consecutive traffic dates before updating CSV files or opening a pull request. This prevents delayed GitHub traffic reporting from producing partial-week updates.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: faeed566-c636-49b1-a92d-44d43d7912f0
Copilot AI balanced review requested due to automatic review settings September 29, 2026 17:15
@DanWahlin
DanWahlin merged commit 2de7b23 into main Sep 29, 2026
6 checks passed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

The date calculation can stall across calendar-year boundaries.

Review effort: Balanced
Findings: 1 High severity

Open (1)
What changed in this PR

Updates the traffic workflow to prevent partial-week PRs.

Changes:

  • Requires seven consecutive, complete dates.
  • No-ops when data is incomplete.
  • Verifies both CSV files receive matching windows.
File Description
.github/​workflows/​traffic-updater.md Defines complete weekly-window validation and retry behavior.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

## Step 3 — Determine the next complete seven-day window

From the API response, keep only entries whose date is **after** the last recorded date from Step 1.
The next collection window starts on the calendar day immediately after the last recorded date and ends six days later.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants