Skip to content

Comments

Update copyright notices (#3818)#3820

Merged
UziTech merged 1 commit intomarkedjs:masterfrom
ziadkh0:issue-3818
Oct 30, 2025
Merged

Update copyright notices (#3818)#3820
UziTech merged 1 commit intomarkedjs:masterfrom
ziadkh0:issue-3818

Conversation

@ziadkh0
Copy link
Contributor

@ziadkh0 ziadkh0 commented Oct 30, 2025

Marked version:

16.4.1

Markdown flavor: n/a

Description

Contributor

  • Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
  • no tests required for this PR.
  • If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

@vercel
Copy link

vercel bot commented Oct 30, 2025

@ziadkh0 is attempting to deploy a commit to the MarkedJS Team on Vercel.

A member of the Team first needs to authorize it.

@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Oct 30, 2025

Summary of Changes

Hello @ziadkh0, 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 addresses the need to update and correct copyright information within the project's source files and documentation. The changes ensure that intellectual property attribution is accurate, reflecting the historical and current ownership structure by clearly distinguishing between the contributions of Christopher Jeffrey and MarkedJS over different time periods.

Highlights

  • Copyright Attribution: Updated copyright notices across various files to reflect ownership by "MarkedJS" for years 2018 onwards, while retaining "Christopher Jeffrey" for the period 2011-2018.
  • Copyright Format Standardization: Standardized the format of copyright notices to clearly delineate the periods of ownership for different entities within the project files.
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. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Oct 30, 2025
View reviewed changes
Copy link
Contributor

@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 updates copyright notices across several files to reflect the transfer of copyright to MarkedJS from 2018 onwards. The changes are consistent and correctly applied in all modified files, including README.md, source files in bin/, the build configuration, and the man page. The updates align with the information in LICENSE.md. The changes are well-executed and I have no further feedback.

@vercel
Copy link

vercel bot commented Oct 30, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
marked-website Ready Ready Preview Comment Oct 30, 2025 2:55pm

UziTech
UziTech approved these changes Oct 30, 2025
View reviewed changes
Copy link
Member

@UziTech UziTech left a comment

Choose a reason for hiding this comment

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

Thanks for doing this! 💯

@UziTech UziTech merged commit ee6b45f into markedjs:master Oct 30, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@UziTech UziTech UziTech approved these changes

+1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

hacktoberfest-accepted

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Inconsistant copyright

2 participants

@ziadkh0 @UziTech