Dependabot: one NuGet group instead of production and development
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- devops
Research direction
Open .github/dependabot.yml and inspect the existing NuGet production and development groups, comparing them with the GitHub Actions group shape shown in the issue. Replace the two NuGet groups with one "NuGet updates" group using the stated pattern, then verify no separate NuGet groups remain.
Written by the indexing model from the issue text.
Description
Why
.github/dependabot.yml splits NuGet into two groups by dependency-type: "NuGet production updates" and "NuGet development updates". The split buys nothing here:
- Every NuGet pull request Dependabot has opened came from the production group (#2, #16, #56, #99). The development group has never opened one.
- CI gates production and development packages alike, so a separate development pull request carries no lower risk and nothing merges it without review.
- The schedule is monthly, so one grouped pull request is easy to review.
SemiPlot took this file as a template and hit the failure mode the split invites: a local tool in .config/dotnet-tools.json landed in both groups, and Semiteq/SemiPlot#100 and Semiteq/SemiPlot#101 each bumped terse from 1.0.0 to 1.1.0. SemiStep has no tool manifest today, so it would hit the same duplicate as soon as it adds one. SemiPlot now uses one group (Semiteq/SemiPlot#107).
What
Replace both NuGet groups with one, in the shape the GitHub Actions group already has:
groups:
"NuGet updates":
patterns:
- "*"
- Dominant language
- C#
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Semiteq/SemiStep
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
The JetBrains retint does not reach Semi's core controlsMay be free again @mrcsin claimed this 37 days ago, and no pull request is open. Openbug
-
Generate the resx accessor with ResxSourceGenerator instead of maintaining it by handMay be free again @mrcsin claimed this 38 days ago, and no pull request is open. Openbug
-
ui/app.yaml is never delivered, so the locale is a silent defaultMay be free again @mrcsin claimed this 38 days ago, and no pull request is open. Openbug
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 38/100
All issues in Semiteq/SemiStep
Similar issues
-
Wrong values of Kernel32.FileShare.Delete and Kernel32.FileAttributes.PosixSemanticsPossibly taken @ElectLive claimed this today. Openbug good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 83/100
ForNeVeR/TruePath#241 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
files-community/Files#19047 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:frontend bug FE hotspot:css P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
klasolsson81/jobbliggaren#2175 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
elsa-workflows/elsa-foundation#2965 ·
Maintainers usually reply within 1 day