chore: add jeremylongshore to CLA signers

[jeremylongshore]

Summary

Adding myself to the CLA signers file to enable CLA checks on my PRs.

• GitHub username: jeremylongshore
• Email: jeremylongshore@gmail.com
• Signed date: 2026-01-11

Related PRs

This unblocks CLA checks for:

• feat: add systemd service helper with plain-English explanations #557 (systemd service helper)
• feat(tarball): Add tarball/source build helper (Issue #452) #558 (tarball helper)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated the list of contributors who have signed the Contributor License Agreement.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[gemini-code-assist]

Summary of Changes

Hello @jeremylongshore, I'm Gemini Code Assist¹! 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 updates the project's Contributor License Agreement (CLA) signers list. By adding a new contributor to this record, it ensures that their subsequent contributions can be properly processed and pass automated CLA verification checks, facilitating smoother integration of their work.

Highlights

• CLA Signer Addition: Added 'jeremylongshore' to the .github/cla-signers.json file, including their name, GitHub username, email, and the date the CLA was signed.
• Unblocks Related PRs: This change unblocks CLA checks for pull requests feat: add systemd service helper with plain-English explanations #557 (systemd service helper) and feat(tarball): Add tarball/source build helper (Issue #452) #558 (tarball helper), allowing them to proceed.

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. ↩

[github-actions]

CLA Verification Failed

The following contributors have not signed the Contributor License Agreement:

• @jeremylongshore (jeremylongshore, jeremylongshore@users.noreply.github.com)
• Claude Opus 4.5 (noreply@anthropic.com)

How to Sign

1. Read the CLA document
2. Open a CLA signature request
3. A maintainer will add you to the signers list
4. Comment recheck on this PR to re-run verification

---

This check runs automatically. Maintainers can update .github/cla-signers.json to add signers.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request adds the author, Jeremy Longshore, to the .github/cla-signers.json file to satisfy the CLA requirement. The change is straightforward and correctly formatted.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds a new contributor's signature entry to the CLA (Contributor License Agreement) signers file. Jeremy Longshore is registered as a signer with their associated GitHub username, email address, and signature date.

Changes

Cohort / File(s)	Summary
CLA Signers Registry .github/cla-signers.json	Added new individual signer entry for Jeremy Longshore (github_username: jeremylongshore) with email and signature metadata

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Add CLA sign #406: Adds a new individual signer entry to the same .github/cla-signers.json individuals array
• Add Ansh Grover to CLA signers #401: Modifies .github/cla-signers.json by adding a new individual signer entry to the same data structure
• Add new CLA signer Swaroop Manchala #415: Adds another new signer object to the .github/cla-signers.json individuals array with identical structure

Suggested reviewers

• mikejmorgan-ai
• Anshgrover23

Poem

🐰 A new name joins the CLA roll,
Jeremy's signature makes us whole,
With username, email, and date so bright,
Our signer list grows, oh what a sight!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete against the template. The Related Issue section (required) is missing, AI disclosure checkbox is not properly marked, and the PR format checklist is absent.	Add the required 'Related Issue' section with issue number, properly complete the AI Disclosure section (checked and described), and include the full Checklist section from the template.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding jeremylongshore to the CLA signers file. It follows the conventional commit format (chore scope) and is concise.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 337522a and aec132b.

📒 Files selected for processing (1)

• .github/cla-signers.json

🔇 Additional comments (1)

.github/cla-signers.json (1)

206-214: LGTM!

The new CLA signer entry is correctly formatted and follows the established schema. All required fields are present and the data matches the PR description.

Minor note: Consider updating the last_updated field on line 3 from "2026-01-03" to "2026-01-11" (or today's date) to reflect this addition.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[Anshgrover23]

LGTM!