The source check I started this evening (run #30) stopped at validation, which is the intended behaviour, on two answers the coding rules didn't know yet:
First sighting "2 Greens": a new option on the form. It's coded as Green, and the row gets a data flag (first sighting answered as '2 Greens') so the original answer is kept. The mapping lives in core/spec/form.yaml (first_sighting_alias).
Row label "Unknown" on a bulk-pasted row: added to the entry values in data/dictionary.yaml.
Workflow fixes. When validation fails, the rebuild step used to run anyway and crash, so the "Source check failed" issue was never opened. Now, when collection update reports a failed build:
The source check I started this evening (run #30) stopped at validation, which is the intended behaviour, on two answers the coding rules didn't know yet:
- **First sighting "2 Greens"**: a new option on the form. It's coded as `Green`, and the row gets a data flag (`first sighting answered as '2 Greens'`) so the original answer is kept. The mapping lives in `core/spec/form.yaml` (`first_sighting_alias`).
- **Row label "Unknown"** on a bulk-pasted row: added to the `entry` values in `data/dictionary.yaml`.
**Workflow fixes.** When validation fails, the rebuild step used to run anyway and crash, so the "Source check failed" issue was never opened. Now, when `collection update` reports a failed build:
- the rebuild is skipped;
- no data pull request is opened;
- the issue always opens, listing the new answers.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The evening source check stopped (correctly) on two answers the coding rules did not know:
- first sighting "2 Greens": a new form option. Coded as Green, with a data flag that keeps the
original answer (first_sighting_alias in core/spec/form.yaml).
- row label "Unknown" on a bulk-pasted row: added to the entry values in data/dictionary.yaml.
Workflow: when `collection update` reports the build failed, skip the rebuild (it would only fail
again) and always open the "Source check failed" issue, so new answers are reported, not lost.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The source check I started this evening (run #30) stopped at validation, which is the intended behaviour, on two answers the coding rules didn't know yet:
Green, and the row gets a data flag (first sighting answered as '2 Greens') so the original answer is kept. The mapping lives incore/spec/form.yaml(first_sighting_alias).entryvalues indata/dictionary.yaml.Workflow fixes. When validation fails, the rebuild step used to run anyway and crash, so the "Source check failed" issue was never opened. Now, when
collection updatereports a failed build:🤖 Generated with Claude Code
kathleen referenced this pull request2026-11-19 03:29:47 +00:00