Skip to content
This repository was archived by the owner on Jun 18, 2026. It is now read-only.

fix: replace iberi22@gmail.com with github profile#2

Open
iberi22 wants to merge 1 commit into
mainfrom
fix/update-maintainer-email
Open

fix: replace iberi22@gmail.com with github profile#2
iberi22 wants to merge 1 commit into
mainfrom
fix/update-maintainer-email

Conversation

@iberi22

@iberi22 iberi22 commented Apr 30, 2026

Copy link
Copy Markdown
Owner

Actualizando referencias de correo a perfil de GitHub https://github.com/iberi22

Summary by CodeRabbit

  • Chores
    • Updated author contact information across project documentation and metadata files, replacing email address with GitHub profile URL for improved public accessibility.

@coderabbitai

coderabbitai Bot commented Apr 30, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

Author contact information is updated across three files: CITATION.cff, README.md, and paper/paper.tex. Email addresses are consistently replaced with a GitHub profile URL, maintaining uniform contact presentation across citation metadata and documentation.

Changes

Cohort / File(s) Summary
Author Contact Updates
CITATION.cff, README.md, paper/paper.tex
Replaced email address with GitHub profile URL across citation metadata, project README, and LaTeX paper documentation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A bunny hops through files today,
Trading emails in every way,
GitHub links now shine so bright,
Contact info feels just right!
Hop along, the change is neat! 🌟

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: replacing an email address with a GitHub profile URL across multiple files (CITATION.cff, README.md, and paper.tex).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/update-maintainer-email

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 0/1 reviews remaining, refill in 60 minutes.

Comment @coderabbitai help to get the list of available commands and usage tips.

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

Copy link
Copy Markdown

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 replaces the author's email address with a GitHub profile URL across CITATION.cff, README.md, and paper.tex. A review comment correctly identifies that using a URL in the email field of CITATION.cff violates the file format specification and suggests using the website field instead.

Comment thread CITATION.cff
- family-names: "Belalcazar"
given-names: "Ivan"
email: "iberi22@gmail.com"
email: "https://github.com/iberi22"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

El campo email en el archivo CITATION.cff debe contener una dirección de correo electrónico válida según la especificación del Citation File Format (CFF). Proporcionar una URL de GitHub en este campo es técnicamente incorrecto y puede causar que las herramientas que procesan este archivo (como el sistema de citación de GitHub o gestores bibliográficos) no funcionen correctamente. Para incluir un enlace a su perfil de GitHub, se debe utilizar el campo website, que es el campo apropiado para este propósito en la versión 1.2.0 de CFF.

    website: "https://github.com/iberi22"

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CITATION.cff`:
- Line 11: Replace the invalid email field in CITATION.cff: remove or rename the
top-level "email" key that currently holds the GitHub URL and add a "website"
key with the same URL string value; ensure the URL remains properly quoted as in
the original value and validate the CFF 1.2.0 schema after change.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 44e8374e-7438-4dc3-b530-38fa27422ebb

📥 Commits

Reviewing files that changed from the base of the PR and between eb08099 and d453a65.

📒 Files selected for processing (3)
  • CITATION.cff
  • README.md
  • paper/paper.tex

Comment thread CITATION.cff
- family-names: "Belalcazar"
given-names: "Ivan"
email: "iberi22@gmail.com"
email: "https://github.com/iberi22"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# Find and examine the CITATION.cff file
git ls-files | grep -i citation

Repository: iberi22/photon-core

Length of output: 76


🏁 Script executed:

# Read the CITATION.cff file
cat -n CITATION.cff | head -20

Repository: iberi22/photon-core

Length of output: 929


🌐 Web query:

CFF 1.2.0 schema author email website fields specification

💡 Result:

In the Citation File Format (CFF) 1.2.0 schema, the 'author' fields (email and website) are specified for both person and entity objects within the 'authors' array (and similarly for 'contact', 'editors', etc.). For person objects (individual authors): - email: type definitions.email (nonempty string, required: false). Usage example: email: "mail@research-project.org" under family-names/given-names. - website: type definitions.url (nonempty string matching URL pattern, required: false). Usage example: website: "https://research-project.org". For entity objects (groups/organizations): - email: type definitions.email (nonempty string, required: false). Usage example: email: "team@research-project.org" under name. - website: type definitions.url (nonempty string matching URL pattern, required: false). Usage example: website: "https://research-software-project.org". These fields are optional and part of the definitions.entity and definitions.person objects used in arrays like authors. The schema is outlined in schema.json (tag 1.2.0), with full details in schema-guide.md.

Citations:


Fix CFF schema violation: replace email with website for the GitHub URL.

The email field in line 11 of CITATION.cff contains a GitHub URL instead of an actual email address. According to CFF 1.2.0 schema, email must be an email address string, while website is the correct field for URLs.

Proposed fix
-    email: "https://github.com/iberi22"
+    website: "https://github.com/iberi22"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
email: "https://github.com/iberi22"
website: "https://github.com/iberi22"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CITATION.cff` at line 11, Replace the invalid email field in CITATION.cff:
remove or rename the top-level "email" key that currently holds the GitHub URL
and add a "website" key with the same URL string value; ensure the URL remains
properly quoted as in the original value and validate the CFF 1.2.0 schema after
change.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant