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

chore: set schedule of lock closed issue #4285

Merged
merged 1 commit into from Jul 16, 2021
Merged

Conversation

Shinigami92
Copy link
Member

@Shinigami92 Shinigami92 commented Jul 16, 2021

Description

Set the schedule back to a value not so aggressive as we made for the bulk processing, see #4278
I set it to every 7-th day, cause 14-day would be to few
In the last 2 weeks we have already more then 70 issues closed, so the process would not catch up if we set it to low

https://github.com/vitejs/vite/search?q=is%3Aissue+is%3Aunlocked+is%3Aclosed+updated%3A%3E%3D2021-07-03&type=issues

Additional context


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Before submitting the PR, please make sure you do the following

  • Read the Contributing Guidelines.
  • Read the Pull Request Guidelines and follow the Commit Convention.
  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
  • Ideally, include relevant tests that fail without this PR but pass with it.

@Shinigami92 Shinigami92 added the p1-chore Doesn't change code behavior (priority) label Jul 16, 2021
@Shinigami92 Shinigami92 self-assigned this Jul 16, 2021
@patak-dev patak-dev merged commit e47a6f2 into main Jul 16, 2021
@patak-dev patak-dev deleted the lock-closed-issues branch July 16, 2021 19:34
aleclarson pushed a commit to aleclarson/vite that referenced this pull request Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p1-chore Doesn't change code behavior (priority)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants