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.

Sign up for GitHub

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

Jump to bottom

chore: lock every day #4346

Merged
merged 1 commit into from
Jul 22, 2021
Merged

chore: lock every day #4346

merged 1 commit into from
Jul 22, 2021

Conversation

Shinigami92
Copy link
Member

Description

Last week we had 55 closed issues within one week, only 50 of them got closed

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 22, 2021
@Shinigami92 Shinigami92 self-assigned this Jul 22, 2021
@patak-dev patak-dev merged commit 9dab51d into main Jul 22, 2021
@Shinigami92 Shinigami92 deleted the lock-every-day branch July 22, 2021 08:01
aleclarson pushed a commit to aleclarson/vite that referenced this pull request Nov 8, 2021
@Shinigami92 @aleclarson
chore: lock every day (vitejs#4346)
3e44e0b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@patak-dev patak-dev patak-dev approved these changes

Assignees

@Shinigami92 Shinigami92

Labels
p1-chore Doesn't change code behavior (priority)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Shinigami92 @patak-dev