Question 1

What does forking a pit do?

Accepted Answer

Forking copies someone else's public pit into your own account as an independent pit you can edit, extend and republish.

It is how you build on a conversation, take a prompt that nearly worked, fork it, refine it and share your improved version, with the lineage back to the original preserved.

Question 2

How do teams collaborate on pits?

Accepted Answer

Create a team workspace and add collaborators by PitHub username or account email. Every member can read, create, edit, append, fork, and comment on pits in that team.

Only the team owner can add or remove members or delete the workspace. Removing a collaborator immediately removes access to every team pit.

Question 3

How does version history work?

Accepted Answer

Every push to a pit, yours or a collaborator's, creates a new version rather than overwriting the last one. The pit always shows the latest, but the earlier versions are kept.

You can read the full history with list_pit_versions, which is how a prompt's evolution stays visible instead of being flattened into a single final state.

Question 4

Is the original author credited when I fork?

Accepted Answer

Yes. A fork records where it came from, so the lineage from your version back to the original stays intact.

That attribution is the point, it lets a good prompt spread while still crediting the person who started it.