Skip to content

Fixed outdated copyright year in error pages (Fixes #70)#101

Open
Yashvi005-bit wants to merge 1 commit intofossasia:masterfrom
Yashvi005-bit:update-copyright-year
Open

Fixed outdated copyright year in error pages (Fixes #70)#101
Yashvi005-bit wants to merge 1 commit intofossasia:masterfrom
Yashvi005-bit:update-copyright-year

Conversation

@Yashvi005-bit
Copy link

@Yashvi005-bit Yashvi005-bit commented Feb 10, 2026

  • Included a Preview link and screenshot showing after and before the changes.
  • Included a description of the change below.
  • Squashed the commits.

Changes done in this Pull Request

  • Fixes # 70

Description / Changes

Updated the copyright year in 404.html and 500.html to reflect the current project period.

Screenshots if any:

image

Before:

image

After:

image

Summary by Sourcery

Enhancements:

  • Align 404 and 500 error page footer copyright text with the full project date range.

@sourcery-ai
Copy link

sourcery-ai bot commented Feb 10, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the copyright notice text at the bottom of the 404 and 500 error pages to reflect the project period 2009–2026 instead of the outdated single year 2016.

File-Level Changes

Change Details Files
Update copyright year range on static error pages to match current project period.
  • Replaced the 2016 copyright year with 2009-2026 in the footer text of the 404 error page.
  • Replaced the 2016 copyright year with 2009-2026 in the footer text of the 500 error page.
404.html
500.html

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • Instead of hardcoding 2009-2026 in multiple files, consider centralizing the copyright text (e.g., via a shared partial/template or variable) to avoid future inconsistencies across pages.
  • If the project prefers not to update these dates manually each year, you might want to use a dynamic year (or year range) rendered at build/runtime to keep the footer current automatically.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Instead of hardcoding `2009-2026` in multiple files, consider centralizing the copyright text (e.g., via a shared partial/template or variable) to avoid future inconsistencies across pages.
- If the project prefers not to update these dates manually each year, you might want to use a dynamic year (or year range) rendered at build/runtime to keep the footer current automatically.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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