Update git properties from release Git-2026.3.5

[N6REJ]

🤖 Automated Module Properties Update

This PR updates the git.properties file with new versions from release Git-2026.3.5.

Changes:

• Extracted assets starting with git (.7z, .exe, or .zip files)
• Added version entries with download URLs
• Maintained semver ordering (newest first)

Release URL: https://github.com/Bearsampp/modules-untouched/releases/tag/Git-2026.3.5

Next Steps:

1. ⏳ Link validation will run automatically
2. ✅ Once validation passes, this PR will auto-merge
3. ❌ If validation fails, please review and fix invalid URLs

[qodo-code-review]

Review Summary by Qodo

Add Git 2.53.0 release to module properties

✨ Enhancement

Walkthroughs

Description

• Add Git version 2.53.0 to module properties
• Update module identifier from composer to git
• Maintain semver ordering with newest version first

Diagram

flowchart LR
  A["Git 2.53.0 Release"] -- "Extract asset" --> B["PortableGit-2.53.0-64-bit.7z.exe"]
  B -- "Add to properties" --> C["git.properties"]
  D["module_name.txt"] -- "Update identifier" --> E["git"]
  C -- "Maintain semver order" --> F["2.53.0 at top"]

Loading

File Changes

1. module_name.txt ⚙️ Configuration changes +1/-1

Update module identifier to git

• Changed module identifier from composer to git
• Reflects the module being updated in this PR

module_name.txt

---

2. modules/git.properties ✨ Enhancement +1/-0

Add Git 2.53.0 version entry

• Added new version entry for Git 2.53.0
• Includes download URL from Git-2026.3.5 release
• Maintains semver ordering with newest version first

modules/git.properties

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Committed module_name artifact 🐞 Bug ⛯ Reliability

Description

module_name.txt appears to be used only as a temporary workflow handoff, but it is being committed
into the PR and will churn on every automated update. This adds noise and increases the likelihood
of PR conflicts without affecting the actual module properties behavior.

Code

module_name.txt[1]

+git

Evidence

The update workflow explicitly writes module_name.txt as an intermediate value, then later reads it
back only to populate workflow outputs / PR metadata. This indicates the file is a workflow artifact
rather than meaningful repository state, so committing it into automated PRs is unnecessary churn.

.github/workflows/update-module-properties.yml[58-71]
.github/workflows/update-module-properties.yml[602-636]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`module_name.txt` is being committed into automated PRs even though it is only used as a temporary handoff between workflow steps. This causes unnecessary diffs and increases the chance of merge conflicts between simultaneous automated PRs.

### Issue Context
The workflow writes `module_name.txt`, then reads it into a step output and uses that output for PR metadata. Once the output is set, the file no longer needs to exist in the working tree.

### Fix Focus Areas
- .github/workflows/update-module-properties.yml[602-636]

### Suggested change
After the `Read module name` step (once `module_info.outputs.module_name` is set), add a step to delete `module_name.txt` so it won’t be included in the commit created by `peter-evans/create-pull-request`. For example:

```yaml
- name: Remove workflow artifact
 if: always()
 run: rm -f module_name.txt
```

(Place it before `Create Pull Request`.)

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more