Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.github/workflows: add awaiting-user-response.yml #1842

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ramosian-glider
Copy link
Member

Introduce the workflow to handle the AwaitingUserResponse label that will help clean up stale issues.

The intended workflow is as follows:

  • when a presumably stale issue requires input from the user, it is manually labeled with AwaitingUserResponse;
  • if this issue is not updated within 90 days, it is closed automatically;
  • if it is updated, the label is automatically removed.

For testing purposes, the update deadline is currently set to two hours (so please do not use AwaitingUserResponse yet!)

Introduce the workflow to handle the AwaitingUserResponse label that will
help clean up stale issues.

The intended workflow is as follows:
 - when a presumably stale issue requires input from the user,
   it is manually labeled with AwaitingUserResponse;
 - if this issue is not updated within 90 days, it is closed automatically;
 - if it is updated, the label is automatically removed.

For testing purposes, the update deadline is currently set to two hours
(so please do not use AwaitingUserResponse yet!)
runs-on: ubuntu-latest

steps:
- name: Checkout code
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we need to check out the code?

repo,
state: 'open',
labels: 'AwaitingUserResponse',
per_page: 100
Copy link
Contributor

Choose a reason for hiding this comment

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

what does the per_page do? does this limit us to 100?

);

const labelAppliedAt = new Date(latestLabelEvent.created_at);
// TODO(glider): use diffDays instead of diffHours once we finish testing.
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: formatting

owner,
repo,
issue_number: issue.number,
body: 'This issue has been automatically closed as it has been marked "AwaitingUserResponse" for more than 90 days with no activity.'
Copy link
Contributor

Choose a reason for hiding this comment

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

should we add some comment to warn that this is about to happen? or explicitly say "if you are still experiencing this, reopen the bug" or something.

@vitalybuka
Copy link
Contributor

Do we want to to move to llvm-project?

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.

3 participants