lucerneclinic.test: .gitignore ignores .github, so workflow changes need force-add
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 8
Description
Problem
While adding the OpenRouter reviewer caller to milllan/lucerneclinic.test, git add .github/workflows/code-review.yml was silently ignored because the repo's .gitignore ignores .github. The caller only landed after a git add -f.
This means any future workflow/change in that repo won't be committed normally — it'll be skipped unless someone remembers -f, so CI updates can silently fail to deploy.
Fix
Remove .github from .gitignore (or add an exception !/.github/workflows/), then re-commit the caller normally.
Acceptance
.github/workflows/code-review.ymlis tracked and updatable with a plaingit add.- Verify by editing the caller and confirming
git statusshows it without-f.
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.
Research direction
Start by checking the target repository’s .gitignore and .github/workflows/code-review.yml. Confirm that the .github ignore rule prevents normal staging, then apply the requested ignore exception or removal and verify that editing the workflow makes git status show it without -f.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100