Conversation
Contributor
WalkthroughAdds four new Markdown policy documents: German and English Sweepstakes Terms (content/sweepstakes-terms.de.md, content/sweepstakes-terms.en.md) defining organizer, participation period (13.03.2026–18.03.2026 23:59 MEZ), eligibility, entry method, prizes, winner selection/notification, shipping, GDPR-compliant data processing, liability, changes/termination, and final provisions; and German and English Testimonial Consent pages (content/testimonial-terms.de.md, content/testimonial-terms.en.md) describing voluntary consent, scope of use, withdrawal rights, legal basis, contact, and timestamps. All additions are informational Markdown content only. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip You can get early access to new features in CodeRabbit.Enable the |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (2)
content/sweepstakes-terms.en.md (1)
116-116: Use an exact “Last updated” date.“March 2026” is too coarse for legal text versioning. Prefer a specific date (e.g., March 13, 2026).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/sweepstakes-terms.en.md` at line 116, Replace the vague "Last updated: March 2026" text with an exact date string (e.g., "Last updated: March 13, 2026") so the legal document has a precise versioning timestamp; locate and update the line containing "_Last updated: March 2026_" in content/sweepstakes-terms.en.md to use a full month, day, and year format.content/sweepstakes-terms.de.md (1)
114-114: „Stand“ mit konkretem Datum angeben.
März 2026ist für rechtliche Versionierung zu ungenau; besser ein exaktes Datum.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/sweepstakes-terms.de.md` at line 114, Replace the vague version marker "_Stand: März 2026_" with a precise date string (e.g. "_Stand: 15. März 2026_") so the document uses an exact legal versioning date; update the text matching "_Stand: März 2026_" to the chosen concrete date in the same italic/markdown format and ensure consistency with other documents' date format if applicable.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@content/sweepstakes-terms.de.md`:
- Line 17: Update the Redbubble country list reference in the sentence that
mentions "die aktuelle Liste kann unter
https://help.redbubble.com/hc/en-us/articles/206705143 eingesehen werden" to fix
the snapshot date: replace or augment the dynamic link with a dated statement
such as "Stand: DD.MM.YYYY" (or "Stand: YYYY-MM-DD") and keep the URL for
reference; ensure the clause that currently lists excluded countries and the
fallback digital gift sentence remain unchanged except for appending the chosen
date after "gemäß Redbubble" so the file's "Redbubble" reference clearly
indicates the specific snapshot date.
- Line 9: Replace the mismatched ASCII closing quote in the sentence starting
"Veranstalter des Gewinnspiels ist die Skymatic GmbH, Am Hauptbahnhof 6, 53111
Bonn, eingetragen im Handelsregister des Amtsgerichts Bonn unter HRB 22635
(nachfolgend „Veranstalter"." by swapping the trailing straight double-quote (")
for the proper German closing quotation mark (U+201C — “) so the opening „ and
closing “ match; update the line in content/sweepstakes-terms.de.md where the
string includes „Veranstalter" accordingly.
In `@content/sweepstakes-terms.en.md`:
- Line 17: The eligibility paragraph references a live Redbubble list which can
change; update the sentence that cites Redbubble (the clause beginning "Please
note, however, that the physical shipment... can be viewed at
https://help.redbubble.com/...") to freeze that external restriction by
appending an exact snapshot date/version — e.g. change "can be viewed at
https://...)" to "can be viewed at https://... (Redbubble list as of
YYYY-MM-DD)" or alternatively include "as of YYYY-MM-DD" immediately after the
enumerated country list so the terms read "Crimea, Cuba, ... and Ukraine (as of
YYYY-MM-DD)". Ensure the chosen date reflects the exact source/version and keep
the rest of the sentence unchanged.
---
Nitpick comments:
In `@content/sweepstakes-terms.de.md`:
- Line 114: Replace the vague version marker "_Stand: März 2026_" with a precise
date string (e.g. "_Stand: 15. März 2026_") so the document uses an exact legal
versioning date; update the text matching "_Stand: März 2026_" to the chosen
concrete date in the same italic/markdown format and ensure consistency with
other documents' date format if applicable.
In `@content/sweepstakes-terms.en.md`:
- Line 116: Replace the vague "Last updated: March 2026" text with an exact date
string (e.g., "Last updated: March 13, 2026") so the legal document has a
precise versioning timestamp; locate and update the line containing "_Last
updated: March 2026_" in content/sweepstakes-terms.en.md to use a full month,
day, and year format.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: b5aafd9a-35cb-46f7-81ed-6447b41e2b5a
📒 Files selected for processing (2)
content/sweepstakes-terms.de.mdcontent/sweepstakes-terms.en.md
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (3)
content/sweepstakes-terms.de.md (2)
9-9:⚠️ Potential issue | 🟡 MinorFix German quotation marks (still unresolved).
Line 9 uses straight ASCII quotes. Please use matching German quotes for legal/document style consistency.
Suggested wording update
-... (nachfolgend "Veranstalter"). +... (nachfolgend „Veranstalter“).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/sweepstakes-terms.de.md` at line 9, Replace the straight ASCII double quotes around "Veranstalter" in the sentence starting with "Veranstalter des Gewinnspiels..." with German quotation marks: use the opening low double quote („) before Veranstalter and the closing high double quote (“) after Veranstalter so the term appears as „Veranstalter“ throughout the document for consistent legal/document style.
17-17:⚠️ Potential issue | 🟠 MajorRedbubble-Länderliste mit Datumsstand fixieren (weiterhin offen).
Line 17 verweist weiterhin auf eine dynamische Drittseite. Bitte den Stand der Einschränkung mit konkretem Datum festhalten, damit Teilnahmebedingungen nach Veröffentlichung stabil bleiben.
Vorschlag
-... Ukraine (gemäß Redbubble; die aktuelle Liste kann unter https://help.redbubble.com/hc/en-us/articles/206705143 eingesehen werden). +... Ukraine (gemäß Redbubble, Stand 13.03.2026; Referenz: https://help.redbubble.com/hc/en-us/articles/206705143).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/sweepstakes-terms.de.md` at line 17, Update the dynamic Redbubble reference in the paragraph that lists excluded countries (the sentence starting "Bitte beachten Sie jedoch, dass der physische Versand...") by fixing the list to a specific snapshot date: add a clear "Stand: YYYY-MM-DD" after the Redbubble link (or replace the link with an archived snapshot URL) so the list of excluded countries is time-stamped and stable for the published terms; ensure the sentence now reads that the list is accurate as of that date and that winners in those territories will receive the digital substitute.content/sweepstakes-terms.en.md (1)
17-17:⚠️ Potential issue | 🟠 MajorFreeze third-party shipping restrictions to a dated snapshot (still unresolved).
Line 17 still ties eligibility/shipping outcomes to a live Redbubble page. Please pin the country restriction list to an explicit “as of” date so terms stay legally deterministic after publication.
Suggested wording update
- ...and Ukraine (per Redbubble; the current list can be viewed at https://help.redbubble.com/hc/en-us/articles/206705143). + ...and Ukraine (per Redbubble, as of March 13, 2026; reference: https://help.redbubble.com/hc/en-us/articles/206705143).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/sweepstakes-terms.en.md` at line 17, Update the shipping restriction sentence on the line starting with "Eligible participants are natural persons who are at least 18 years of age..." so it no longer ties outcomes to a live Redbubble page; replace the parenthetical Redbubble reference with a pinned snapshot and an "as of" date (e.g., "as of YYYY-MM-DD") and optionally include an archived/immutable URL (archive.org) for the referenced list so the restricted-country outcome is legally deterministic; ensure the clause that winners in those territories receive a digital alternative remains unchanged.
🧹 Nitpick comments (3)
content/sweepstakes-terms.en.md (2)
116-116: Make “Last updated” date exact.Line 116 uses month-only precision (“March 2026”). Use a concrete date for auditability/versioning of legal text.
Suggested wording update
-_Last updated: March 2026_ +_Last updated: March 13, 2026_🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/sweepstakes-terms.en.md` at line 116, Replace the ambiguous "Last updated: March 2026" string with a concrete date to ensure auditability; locate the exact markdown line containing "_Last updated: March 2026_" in content/sweepstakes-terms.en.md and change it to a full date (e.g., "Last updated: March 12, 2026" or "Last updated: 2026-03-12") in the same line so the document records an exact update timestamp.
13-13: Use unambiguous 24-hour time format in the legal window.Line 13 currently uses “11:59 PM (CET)”. For legal clarity and consistency with the German file, prefer
23:59 CET.Suggested wording update
- ...ends on March 18, 2026 at 11:59 PM (CET). + ...ends on March 18, 2026 at 23:59 CET.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/sweepstakes-terms.en.md` at line 13, Update the time format in the sweepstakes period sentence: locate the line that reads "The sweepstakes begins on March 13, 2026 and ends on March 18, 2026 at 11:59 PM (CET)" and replace the 12-hour timestamp "11:59 PM (CET)" with the unambiguous 24-hour format "23:59 CET" so the sentence ends with "March 18, 2026 at 23:59 CET".content/sweepstakes-terms.de.md (1)
115-115: „Stand“-Datum präzisieren.Line 115 ist nur auf Monatsebene angegeben. Ein konkretes Datum verbessert Nachvollziehbarkeit und Versionierung der Teilnahmebedingungen.
Vorschlag
-_Stand: März 2026_ +_Stand: 13.03.2026_🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/sweepstakes-terms.de.md` at line 115, Die Zeile mit dem Versionsdatum "_Stand: März 2026_" ist zu unspezifisch; ersetze diesen Text durch ein konkretes Tagesdatum (z. B. "_Stand: 15. März 2026_" oder ISO-Format "_Stand: 2026-03-15_") so dass das Feld exakt nachvollziehbar ist; aktualisiere den String "_Stand: März 2026_" in content/sweepstakes-terms.de.md (Suche nach genau diesem Text) und achte darauf, dass das Format konsistent zu anderen Dokumenten ist.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@content/sweepstakes-terms.de.md`:
- Line 9: Replace the straight ASCII double quotes around "Veranstalter" in the
sentence starting with "Veranstalter des Gewinnspiels..." with German quotation
marks: use the opening low double quote („) before Veranstalter and the closing
high double quote (“) after Veranstalter so the term appears as „Veranstalter“
throughout the document for consistent legal/document style.
- Line 17: Update the dynamic Redbubble reference in the paragraph that lists
excluded countries (the sentence starting "Bitte beachten Sie jedoch, dass der
physische Versand...") by fixing the list to a specific snapshot date: add a
clear "Stand: YYYY-MM-DD" after the Redbubble link (or replace the link with an
archived snapshot URL) so the list of excluded countries is time-stamped and
stable for the published terms; ensure the sentence now reads that the list is
accurate as of that date and that winners in those territories will receive the
digital substitute.
In `@content/sweepstakes-terms.en.md`:
- Line 17: Update the shipping restriction sentence on the line starting with
"Eligible participants are natural persons who are at least 18 years of age..."
so it no longer ties outcomes to a live Redbubble page; replace the
parenthetical Redbubble reference with a pinned snapshot and an "as of" date
(e.g., "as of YYYY-MM-DD") and optionally include an archived/immutable URL
(archive.org) for the referenced list so the restricted-country outcome is
legally deterministic; ensure the clause that winners in those territories
receive a digital alternative remains unchanged.
---
Nitpick comments:
In `@content/sweepstakes-terms.de.md`:
- Line 115: Die Zeile mit dem Versionsdatum "_Stand: März 2026_" ist zu
unspezifisch; ersetze diesen Text durch ein konkretes Tagesdatum (z. B. "_Stand:
15. März 2026_" oder ISO-Format "_Stand: 2026-03-15_") so dass das Feld exakt
nachvollziehbar ist; aktualisiere den String "_Stand: März 2026_" in
content/sweepstakes-terms.de.md (Suche nach genau diesem Text) und achte darauf,
dass das Format konsistent zu anderen Dokumenten ist.
In `@content/sweepstakes-terms.en.md`:
- Line 116: Replace the ambiguous "Last updated: March 2026" string with a
concrete date to ensure auditability; locate the exact markdown line containing
"_Last updated: March 2026_" in content/sweepstakes-terms.en.md and change it to
a full date (e.g., "Last updated: March 12, 2026" or "Last updated: 2026-03-12")
in the same line so the document records an exact update timestamp.
- Line 13: Update the time format in the sweepstakes period sentence: locate the
line that reads "The sweepstakes begins on March 13, 2026 and ends on March 18,
2026 at 11:59 PM (CET)" and replace the 12-hour timestamp "11:59 PM (CET)" with
the unambiguous 24-hour format "23:59 CET" so the sentence ends with "March 18,
2026 at 23:59 CET".
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: e1bb3a5b-ed20-4a92-9694-c219eb2fee79
📒 Files selected for processing (2)
content/sweepstakes-terms.de.mdcontent/sweepstakes-terms.en.md
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (1)
content/testimonial-terms.de.md (1)
39-39: Use a full effective date instead of month-only status.
_Stand: März 2026_is understandable, but a concrete date (e.g.,13. März 2026) improves legal traceability for future revisions.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@content/testimonial-terms.de.md` at line 39, Replace the month-only effective date string `_Stand: März 2026_` with a full concrete date (day, month, year) for legal traceability—for example `_Stand: 13. März 2026_`—so update the markdown line containing `_Stand: März 2026_` accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@content/testimonial-terms.de.md`:
- Line 39: Replace the month-only effective date string `_Stand: März 2026_`
with a full concrete date (day, month, year) for legal traceability—for example
`_Stand: 13. März 2026_`—so update the markdown line containing `_Stand: März
2026_` accordingly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 6e0ed218-0c7a-4f26-88f2-7a0dda4453dc
📒 Files selected for processing (2)
content/testimonial-terms.de.mdcontent/testimonial-terms.en.md
✅ Files skipped from review due to trivial changes (1)
- content/testimonial-terms.en.md
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
3 participants
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.
No description provided.