Change dependabot schedule to daily #8982
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #8982 +/- ##
==========================================
- Coverage 76.80% 76.79% -0.02%
==========================================
Files 592 592
Lines 24716 24716
==========================================
- Hits 18983 18980 -3
- Misses 5733 5736 +3 ☔ View full report in Codecov by Sentry. |
yufeih
added
the
engineering
p-kostov
pushed a commit
to ErpNetDocs/docfx
that referenced
this pull request
Jun 28, 2024
Change dependabot schedule from weekly to daily
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've created this PR from by following reason.
open-pull-requests-limit(default:5).Remaining PR is not created until next schedule (?)
(I don't confirm behaviors. but currently
semver 6.3.1package update PR is not created.and occurs
moderate severity vulnerabilitymessage when runningnpm installcommand)If software is updated before PR created & merged. It might lead to CI error (e.g.
NuGet.Framewroksupdate)