TL;DR

Add sort=created to the API request in scripts/auto-close-duplicates.ts to align the sort order with the filter logic.

Guidance

• Review the API documentation to ensure sort=created is a valid parameter and understand its implications on the response.
• Update the API request in scripts/auto-close-duplicates.ts to include the sort=created parameter, ensuring the sort order matches the filter condition.
• Test the updated script to verify that issues are correctly paginated and filtered based on their creation time.
• Consider adding logging or monitoring to detect any unexpected behavior or performance changes after implementing the fix.

Example

// Example API request update in scripts/auto-close-duplicates.ts
const response = await fetch(`https://api.example.com/issues?sort=created`);

Notes

This fix assumes that sorting by creation time is the desired behavior. If sorting by update time is preferred, the filter condition should be updated to use updated_at instead.

Recommendation

Apply workaround: Add sort=created to the API request, as it directly addresses the mismatch between the sort order and filter logic, ensuring that issues are processed efficiently and correctly.