[repo-assist] eng: remove dead .paket CI cache step
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- github-actions, yaml
- Domain
- ci-cd
Research direction
Open .github/workflows/dotnetcore.yml and locate the “Cache .paket directory” step described in the issue. Remove that step, keep the following dotnet tool restore and NuGet cache steps unchanged, and review the workflow diff to confirm this is the only CI configuration change.
Written by the indexing model from the issue text.
Description
🤖 This PR was created by Repo Assist, an automated AI assistant.
Summary
The dotnetcore.yml CI workflow contained a cache step for the .paket directory:
- name: Cache .paket directory
uses: actions/cache@v5
with:
path: .paket
key: $\{\{ runner.os }}-paket-$\{\{ hashFiles('**/paket.lock') }}
restore-keys: |
$\{\{ runner.os }}-paket-
This directory does not exist in the repository. Paket is installed as a dotnet local tool via .config/dotnet-tools.json, so its binaries live under ~/.nuget/packages/paket/10.3.1/... — already covered by the existing Cache NuGet packages step.
Effect
On every CI run, the cache action:
- Attempts to restore a cache hit for a path that doesn't exist (no-op).
- Computes a cache key for an empty/non-existent directory (wasted work).
- On cache miss, tries to save an empty snapshot (waste of storage).
Change
Remove the dead cache step. The dotnet tool restore step that follows is unaffected — paket will continue to be resolved from the NuGet packages cache as before.
Test Status
CI configuration change only — no code changes. The existing build pipeline remains identical; this simply removes an ineffective step that adds log noise and cache overhead on every run.
[!WARNING]
Protected Files — Push Permission DeniedThis was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.
Protected files
The push was rejected because GitHub Actions does not have
workflowspermission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.
Create the pull request manually
# Download the patch from the workflow run
gh run download 25055192070 -n agent -D /tmp/agent-25055192070
# Create a new branch
git checkout -b repo-assist/eng-remove-dead-paket-cache-20260428-5861b1cc0b9eee98 master
# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-25055192070/aw-repo-assist-eng-remove-dead-paket-cache-20260428.patch
# Push the branch and create the pull request
git push origin repo-assist/eng-remove-dead-paket-cache-20260428-5861b1cc0b9eee98
gh pr create --title '[Repo Assist] eng: remove dead .paket CI cache step' --base master --head repo-assist/eng-remove-dead-paket-cache-20260428-5861b1cc0b9eee98 --repo fsprojects/SwaggerProvider
Generated by 🌈 Repo Assist, see workflow run. Learn more.
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/repo-assist.md@3de4e604a36b5190a1c7dc4719c7341500ba8a95
- Dominant language
- F#
- Stars
- 278
- Forks
- 60
- Avg merge
- 4h 26m
- Merged PRs (30d)
- 8
Contributor guide
No contributing guide indexed for this repository
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 fsprojects/SwaggerProvider
-
bug needs investigation
Difficulty 3/5 1-2 days Newbie friendliness 64/100
fsprojects/SwaggerProvider#490 · 2 comments ·
-
automation documentation repo-assist
Difficulty 5/5 Over a week Newbie friendliness 5/100
fsprojects/SwaggerProvider#489 ·
-
automation blocked enhancement repo-assist
Difficulty 4/5 3-5 days Newbie friendliness 42/100
fsprojects/SwaggerProvider#358 · 2 comments ·
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
fsprojects/SwaggerProvider#33 · 2 comments ·
All issues in fsprojects/SwaggerProvider
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·