Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Template update requires manual application (a595095f2ed57bb5d0412a6d7cc656d4cacab9a5)

Closed Beginner friendly
#76 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

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
ci-cd, devops

Research direction

Open .github/renovate.json and compare it with the supplied diff. Add the package rule that excludes .github/workflows/*.lock.yml from Renovate updates, then validate that the file remains valid JSON and the configuration matches the requested semantics.

Written by the indexing model from the issue text.

Description

Template workflows have been updated but the diff could not be automatically applied to this repository. Apply a change that is semantically equivalent to the patch here.

Commit

Exclude gh-aw generated lock files from Renovate (#530)

Co-authored-by: Claude Sonnet 5.5 [email protected]

See: https://github.com/plengauer/plengauer.github.io/commit/a595095f2ed57bb5d0412a6d7cc656d4cacab9a5

Diff

diff --git a/.github/renovate.json b/.github/renovate.json
index 9a19585..3786cd2 100644
--- a/.github/renovate.json
+++ b/.github/renovate.json
@@ -10,5 +10,12 @@
   "prConcurrentLimit": 0,
   "automerge": true,
   "ignoreTests": true,
-  "lockFileMaintenance": { "enabled": true }
+  "lockFileMaintenance": { "enabled": true },
+  "packageRules": [
+    {
+      "description": "Generated by gh aw compile from the .md sources; must not be updated by hand",
+      "matchFileNames": [".github/workflows/*.lock.yml"],
+      "enabled": false
+    }
+  ]
 }

Dominant language
C++
Stars
2
Forks
0
Avg merge
13m
Merged PRs (30d)
20

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from plengauer/DXGIOutputDuplication

All issues in plengauer/DXGIOutputDuplication

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.