Stop tracking generated persona JSON artifacts

Merged
KH
5mo ago
+1-221

User description

Summary

  • Remove the root */persona.json files introduced by #23 for generated persona outputs.
  • Add */persona.json to .gitignore so future npm run compile output stays local.
  • Leave handler code and pre-existing tracked artifacts such as review/.workforce/build/* untouched.

Deploy/compile convention checked

  • Repo docs state the local workflow is: agentworkforce persona compile ./<agent>/persona.ts, then agentworkforce deploy ./<agent>/persona.json --mode cloud.
  • I verified with dry-runs that a committed linear/persona.json is neither required nor sufficient for deploy: both linear/persona.ts and linear/persona.json currently fail the same cloud trigger validation in this repo state, so no persona requires these generated JSON files to be tracked.
  • The correct convention is local compile -> local gitignored persona.json -> deploy; do not commit the generated output.

Validation

  • npm run typecheck
  • npm test
  • npm run compile (confirmed generated root persona JSON files are recreated locally and ignored)
  • git check-ignore --no-index -v granola/persona.json linear/persona.json review/persona.json

Summary by cubic

Stop tracking generated persona.json outputs by removing committed files and adding */persona.json to .gitignore. This keeps compile artifacts local and out of Git history.

CodeAnt-AI Description

Stop committing generated persona JSON files

What Changed

  • Removed generated persona.json files from the repo for the affected personas
  • Future persona builds will keep these generated files local instead of checking them into Git

Impact

✅ Cleaner repository history
✅ Fewer accidental commits of generated files
✅ Easier local compile-and-deploy workflow

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.