Skip to content

feat: adding build date to the templates#352

Merged
jaredwray merged 3 commits intomainfrom
feat-adding-build-date-to-the-templates
Mar 13, 2026
Merged

feat: adding build date to the templates#352
jaredwray merged 3 commits intomainfrom
feat-adding-build-date-to-the-templates

Conversation

@jaredwray
Copy link
Owner

@jaredwray jaredwray commented Mar 13, 2026

Please check if the PR fulfills these requirements

  • Followed the Contributing and Code of Conduct guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feat: adding build date to the templates

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new feature to display the last modification date on generated pages. By adding a lastModified property to core data structures and populating it from relevant sources, users can now see when content was last updated. This enhancement improves transparency and can be beneficial for content freshness and SEO.

Highlights

  • New lastModified property: Introduced a lastModified string property to DoculaChangelogEntry, DoculaData, and DoculaDocument types to store the last modification date of content.
  • Date Population Logic: Implemented logic to populate the lastModified property for documents and changelog entries, deriving it from file system modification times or GitHub release dates, formatted as YYYY-MM-DD.
  • Footer Display: Added a conditional display in the modern theme's footer to show the lastModified date if available for the current page.
  • Styling for Dates: Included new CSS rules to style the lastModified date displayed in the footer.
  • Enhanced Test Coverage: Updated existing tests and added new dedicated test cases to ensure the lastModified property is correctly set and formatted across various content types.
Changelog
  • src/builder.ts
    • Added lastModified property to DoculaChangelogEntry, DoculaData, and DoculaDocument interfaces.
    • Implemented logic to set doculaData.lastModified for pages without specific source files.
    • Updated parseChangelogEntry to include lastModified from file modification time or release date.
    • Updated parseDocumentData to include lastModified from file modification time.
  • templates/modern/css/styles.css
    • Added .footer__updated CSS class for styling the last modified date in the footer.
  • templates/modern/includes/footer.hbs
    • Added a Handlebars conditional to display the lastModified date in the footer if present.
  • test/builder.test.ts
    • Updated numerous existing test expectations to include the new lastModified property.
    • Added new test suite for lastModified field, verifying its presence and YYYY-MM-DD format for documents, changelog entries, and GitHub releases.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@codecov
Copy link

codecov bot commented Mar 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (c97da55) to head (31a2e18).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #352   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            7         7           
  Lines         1575      1576    +1     
  Branches       460       460           
=========================================
+ Hits          1575      1576    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a lastModified date to various data types and templates, which will be displayed in the footer. The implementation correctly sources the modification date from file metadata for documents and changelog entries, and from the release's publication date for GitHub releases. For pages without a direct source file, it defaults to the build date. The changes are well-tested. I've identified a couple of opportunities to improve performance by avoiding redundant file system calls.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 791dbf9c63

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@jaredwray jaredwray merged commit 606afaa into main Mar 13, 2026
9 checks passed
@jaredwray jaredwray deleted the feat-adding-build-date-to-the-templates branch March 13, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant