Skip to content

chore: Stop tracking dotagents-managed artifacts - #18797

Merged
szokeasaurusrex merged 2 commits into
masterfrom
chore/untrack-dotagents-artifacts
Jul 23, 2026
Merged

chore: Stop tracking dotagents-managed artifacts#18797
szokeasaurusrex merged 2 commits into
masterfrom
chore/untrack-dotagents-artifacts

Conversation

@szokeasaurusrex

Copy link
Copy Markdown
Member

dotagents now manages agents.lock and .agents/.gitignore as local state and expects them gitignored. Remove the tracked leftovers, drop the stale comment in agents.toml, and document in AGENTS.md that skills must be installed via 'make develop'.

The .gitignore and agents.toml changes are per 'dotagents doctor --fix' recommendations.

dotagents now manages agents.lock and .agents/.gitignore as local state and expects them gitignored. Remove the tracked leftovers, drop the stale comment in agents.toml, and document in AGENTS.md that skills must be installed via 'make develop'.

The .gitignore and agents.toml changes are per 'dotagents doctor --fix' recommendations.
@vercel

vercel Bot commented Jul 22, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
develop-docs Ready Ready Preview Jul 22, 2026 2:45pm
sentry-docs Ready Ready Preview Jul 22, 2026 2:45pm

Request Review

@szokeasaurusrex
szokeasaurusrex requested review from dcramer and sfanahata and removed request for dcramer July 22, 2026 14:33
@sfanahata

Copy link
Copy Markdown
Contributor

@szokeasaurusrex - thank you for cleaning this up. What is the expected workflow here for people working with agents? Is it that they run make develop after a master pull or cloning the repo?

I want to think through how to make that explicit outside of AGENTS.md, since I doubt that folks pulling down the repo will be checking that file with any regularity.

@sfanahata sfanahata left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nothing blocking, but I have UX questions around how to properly instruct contributors on consistently getting skills and up to date skills to their cloned repo.

@szokeasaurusrex

Copy link
Copy Markdown
Member Author

What is the expected workflow here for people working with agents? Is it that they run make develop after a master pull or cloning the repo?

@sfanahata Yeah, I believe so. To be honest, I am not a dotagents expert, but it appears that it is recommended to run dotagents install after pulling (this should be getting run by make develop in this repo). dotagents is documented in more depth on its landing page.

The main reason I raised this PR was because I noticed some skills were missing when I pulled this repo after some time of not working with it, and running dotagents install modified the checked-in skill files, because they were out of date with the dotagents-managed versions. This PR is intended only to fix the misconfiguration in this repo; it may be worth defining some automations to help folks keep dotagents up to date, e.g. via a git hook that runs after pull.

@szokeasaurusrex
szokeasaurusrex merged commit 276b3c8 into master Jul 23, 2026
22 checks passed
@szokeasaurusrex
szokeasaurusrex deleted the chore/untrack-dotagents-artifacts branch July 23, 2026 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants