Auto PR: Scheduled addition of new claims#40
Merged
Conversation
📝 WalkthroughWalkthroughNine new YAML claim records are added across distinct news source directories. Each file contains four fields—sourceUriDigest, summary, title, and uri—capturing metadata for news articles from BBC, Fox News, Hindustan Times, India Times, NDTV, South China Morning Post, The Guardian, The New York Times, and Yahoo Finance. ChangesClaim Records Addition
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@claims/bbc/tasmanian_government_apologise.yaml`:
- Around line 1-4: The YAML files use JSON-style quoted keys which is invalid;
update claims/bbc/tasmanian_government_apologise.yaml and the other 7 claim
files to use proper YAML key syntax by removing quotes around keys like
sourceUriDigest, summary, title, and uri and ensure each mapping uses unquoted
keys with colon separators and valid YAML string values; validate each file
after editing (e.g., a YAML linter) to confirm correct parsing and consistent
format across all claims.
- Around line 1-4: Convert the block to valid YAML (use key: value without
quoted keys and colons inside quotes) and replace the incorrect
"sourceUriDigest" key with the required uriDigest field set to the SHA-256 hash
of the uri value; keep title, summary and uri as normal YAML keys and add the
missing required boolean fields checked: false and validity: false so the Claim
schema is satisfied.
In `@claims/yahoo_finance/avax_one_avx_q1_2026_earning.yaml`:
- Line 2: The "summary" field in
claims/yahoo_finance/avax_one_avx_q1_2026_earning.yaml is truncated after
"highlighted by an LOI"; update the "summary" value to complete the sentence
with the LOI's context (e.g., counterparty or purpose and next steps), so it
reads as a full statement about the Letter of Intent and its role in AVAX One's
pivot toward AI/HPC infrastructure.
- Around line 1-4: The YAML uses JSON-style quoted keys; change each quoted key
("sourceUriDigest", "summary", "title", "uri") to plain YAML keys
(sourceUriDigest:, summary:, title:, uri:) and ensure values remain valid YAML
(quote value strings only if they contain special characters); update the block
so it is valid YAML mapping syntax (key: value pairs) matching the existing keys
from the diff.
- Around line 1-4: The file is currently using JSON-style quoted keys and is
missing required claim fields; convert the document to valid YAML (remove
surrounding quotes from keys and use YAML mapping syntax) and add the three
missing schema fields: uriDigest, checked, and validity (populate uriDigest with
the computed/expected digest or same as sourceUriDigest if appropriate, set
checked to a boolean, and set validity to the correct enum/string value), or if
this is only creation input (ClaimInput) mark/format it accordingly and omit
those stored-claim fields; update the keys referenced in the diff
(sourceUriDigest, summary, title, uri) to YAML format while ensuring the
presence/values of uriDigest, checked, and validity.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ebb72038-a38f-4040-b5c4-ee7e8e752e6d
📒 Files selected for processing (9)
claims/bbc/tasmanian_government_apologise.yamlclaims/fox_news/american_tourists_arrested_in.yamlclaims/hindustan_times/at_least_nine_dead_in_china_af.yamlclaims/india_times/farm_fires_punjab_reports_115.yamlclaims/ndtv/free_chatgpt_plus_for_everyone.yamlclaims/south_china_morning_post/hong_kong_records_10_tremor_re.yamlclaims/the_guardian/california_island_fire_linked.yamlclaims/the_new_york_times/meta_reassigns_7_000_employees.yamlclaims/yahoo_finance/avax_one_avx_q1_2026_earning.yaml
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 9 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds claims made by the ingested sources in the last week for ingestion
Summary by CodeRabbit