add upcoming conferences

[swillemin-dh]

Pull request

Proposed changes

Types of changes

• New feature (non-breaking change which adds functionality).
• Enhancement (non-breaking change which enhances functionality)
• Bug Fix (non-breaking change which fixes an issue).
• Breaking change (fix or feature that would cause existing functionality to change).

Checklist

• I have read the README document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

Summary by CodeRabbit

• Documentation
  • Reorganized events section with improved formatting and enhanced date presentation
  • Added two new upcoming conferences (June 2026 and November 2026)
  • Enhanced event listings with structured metadata, including location and session details

[coderabbitai]

Walkthrough

Restructured the "Bit Philology events" section in the project file with date- and category-specific subsections. Replaced a single-line workshop entry with verbose formatting including nested metadata. Added two new conference entries for June and November 2026, while retaining the existing Humanistica 2026 poster slot.

Changes

Cohort / File(s)	Summary
Bit Philology Events content/projects/bitphilology/index.qmd	Restructured events section with date- and category-specific subsections. Reformatted workshop entry with verbose day-month format and nested metadata. Added two new conference entries (June 3–5 and November 13–14, 2026) with event details and updated wording.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is largely empty, containing only the template structure with no content filled in for proposed changes or specific details about the modifications.	Complete the 'Proposed changes' section by explaining what conferences were added, why they matter, and provide brief details about the updates to the events section.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'add upcoming conferences' clearly describes the main change—adding new conference entries to the Bit Philology events section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bit-philology-update

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

content/projects/bitphilology/index.qmd (1)

22-29: Optional: normalize date style for consistency.

Consider using one consistent pattern for ranges (e.g., 20–22 May 2026, 03–05 June 2026, 13–14 November 2026) to match the polished structure you introduced.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/projects/bitphilology/index.qmd` around lines 22 - 29, Normalize the
date ranges to a consistent style by replacing hyphens with en-dashes and
zero-padding single-digit days where used; specifically update the three entries
currently written as "20-22 May 2026", "3-5 June 2026", and "13-14 November
2026" to a uniform format such as "20–22 May 2026", "03–05 June 2026", and
"13–14 November 2026" so all ranges use an en-dash and consistent day
formatting.

🤖 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/projects/bitphilology/index.qmd`:
- Around line 22-29: Normalize the date ranges to a consistent style by
replacing hyphens with en-dashes and zero-padding single-digit days where used;
specifically update the three entries currently written as "20-22 May 2026",
"3-5 June 2026", and "13-14 November 2026" to a uniform format such as "20–22
May 2026", "03–05 June 2026", and "13–14 November 2026" so all ranges use an
en-dash and consistent day formatting.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 26081e09-6b09-4459-b5de-8e8b1f75ff1a

📥 Commits

Reviewing files that changed from the base of the PR and between e95acb4 and 209a5ac.

📒 Files selected for processing (1)

• content/projects/bitphilology/index.qmd