Repository navigation
Replace maintainer placeholders with canonical author/contact profiles across docs - #1
Merged
Merged
Conversation
Co-authored-by: Shree-hari <31119605+Shree-hari@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR replaces maintainer/developer placeholder metadata with concrete, canonical author/contact details across contributor-facing documentation so readers can find consistent project-owner identity information.
Changes:
- Updated README “Developer” section and documentation links/map labels to remove placeholder wording.
- Populated
docs/DEVELOPER.mdprofile table with maintainer identity details (leaving release-identity placeholders intact). - Added maintainer contact section to
CONTRIBUTING.mdand replaced placeholders inAUTHORS.md.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| README.md | Replaces placeholder developer narrative with published maintainer identity details and updates map/link labels. |
| docs/DEVELOPER.md | Fills in developer profile fields that were previously TO BE PROVIDED. |
| CONTRIBUTING.md | Adds a Maintainer section with canonical contact/social links. |
| AUTHORS.md | Replaces maintainer placeholders with concrete creator/contact profile values. |
Suppressed comments (1)
docs/DEVELOPER.md:13
- In the profile table, the “Website” field is currently being used as the X profile URL, and “Private security contact” is labeled as private despite being published here. This makes the published identity fields inconsistent with README/CONTRIBUTING/AUTHORS and the intent of the field names.
| GitHub username | [@Shree-hari](https://github.com/Shree-hari) |
| Website | https://x.com/it_is_harsh |
| Support contact | harshmacc@gmail.com |
| Private security contact | harshmacc@gmail.com |
| LinkedIn | https://www.linkedin.com/in/shree-hari/ |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| This page reserves the public project-owner information. Replace every | ||
| `TO BE PROVIDED` value before publishing the repository. | ||
| This page contains the public project-owner information. |
Comment on lines
+231
to
+234
| - Name: Harsh Jhunjhunuwala | ||
| - Email: harshmacc@gmail.com | ||
| - X: https://x.com/it_is_harsh | ||
| - LinkedIn: https://www.linkedin.com/in/shree-hari/ |
Comment on lines
+38
to
+41
| - Name: Harsh Jhunjhunuwala | ||
| - Email: harshmacc@gmail.com | ||
| - X: https://x.com/it_is_harsh | ||
| - LinkedIn: https://www.linkedin.com/in/shree-hari/ |
| - Contact: `TO BE PROVIDED` | ||
| - Name: Harsh Jhunjhunuwala | ||
| - GitHub: https://github.com/Shree-hari | ||
| - Contact: harshmacc@gmail.com |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This update removes placeholder maintainer metadata and standardizes project-owner identity details across contributor-facing documentation. Author name, email, and social profiles are now consistently published where readers expect them.
Maintainer identity rollout
/AUTHORS.mdwith canonical maintainer details:README alignment
Contributor/developer docs consistency
/CONTRIBUTING.mdwith the same canonical contact/social links./docs/DEVELOPER.mdtable entries fromTO BE PROVIDEDto concrete profile values while leaving release-identity fields unchanged.