Skip to content

Conversation

@Madhu696969
Copy link

This pull request adds a short explanation about the MIT License section in the README to make it clearer for contributors and readers.

Changes made

Added a brief note explaining the scope of the MIT License and what it covers.

Ensured formatting aligns with existing README style and tone.

Reason for change

The README mentions the MIT License but does not clarify its purpose.
This update helps contributors better understand how the code portions of the repository are licensed differently from documentation content (which uses Creative Commons Attribution 4.0).

Checklist
Followed contribution guidelines
Markdown formatting verified
Content reviewed for clarity and tone

@welcome
Copy link

welcome bot commented Nov 4, 2025

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Nov 4, 2025
@Sharra-writes
Copy link
Contributor

@Madhu696969 Thanks for opening a PR! Unfortunately, the README isn't a good place for this explanation. It's easy to look up what an MIT License is, and we want our contributing docs to be essential information only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants