ci: unassign issues stale 14 days ago

[tisonkun]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

This closes #3525.

What's changed and what's your intention?

Perhaps we can add more detailed conditions. Welcome to leave a comment :D

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR does not require documentation updates.

[tisonkun]

This is a demonstration unassign action.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.34%. Comparing base (74862f8) to head (3c34d7c).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3529      +/-   ##
==========================================
- Coverage   85.35%   85.34%   -0.02%     
==========================================
  Files         906      906              
  Lines      151023   151023              
==========================================
- Hits       128913   128896      -17     
- Misses      22110    22127      +17     

[sunng87]

May I know the criteria for an issue being inactive?

[tisonkun]

@sunng87 currently it checks the "updated_at" of the issue property.

The logic is here.

I created https://github.com/tisonspieces/auto-unassign/issues/2 for any further conditions we'd like to refine.