Collaboration

Forks

Fork copies a public list into your account with a visible "forked from" attribution. Your fork evolves independently — its versions are yours. Fork when you want your variant; suggest an edit when you want to improve the original.

Suggestions

Anyone can open a suggestion on a public list: change, add or remove blocks with a note. The suggestion page works like a pull request, split into tabs:

• Conversation — threads on the suggestion;
• Proposed changes — the diff, with a count of changed items;
• Checks — conditions that block acceptance;
• Result — what the list will become if the suggestion is accepted: the finished view a reader sees (not a diff), labeled "becomes vN+1";
• Commits — only for suggestions from a branch.

An accepted suggestion becomes a new version of the list with attribution.

Comments on an item

In the diff you can "Comment on item" — the comment anchors to a specific block and field (title, description, command…), or to the exact quote if you select text. Across edits the anchor honestly shows its state: "re-anchored" or "the quoted text is gone". Post a comment right away ("Send") or hold it in a review ("Add to review" — a draft only you see until you submit the whole review). A thread can be marked "Resolved" / "Reopen" or moved to an issue.

You can attach a ready field text to a comment with "Suggest text" — anyone with edit rights presses "Apply" and the text replaces the field.

The review verdict is "Approve" or "Request changes"; requested changes block acceptance until they're cleared.

Branches and merging

A suggestion can live on a branch. In the version bar the "Branches" picker creates a branch ("New branch…" → "Create") from the current one; on a branch the list is a draft and no versions are made. When the branch has changes, "Open pull request" opens a suggestion from it (or push the branch via git — Git access).

Merge such a suggestion with "Merge into main" (or "Squash and merge"); if the branch is behind, "Update from main" pulls changes in, and conflicts are handled by the built-in resolver. An ordinary suggestion (no branch) is simply accepted or rejected by the owner.

Issues

Each list has an issue tracker (enabled by the owner): numbered issues (#1, #2…) with an open / closed status, comments and emoji reactions. Issues are about "do or fix" — problems and ideas not yet shaped into an edit.

• Labels — a built-in set (bug, enhancement, question, docs, help wanted, won't fix, broken link) plus the list's own colored labels.
• Milestones — group issues under a dated goal and show progress.
• Assignees — set by the owner or a collaborator. Assign a master expert and it takes on the task itself.

Discussions

A section separate from issues (also enabled by the owner) — free-form threads at the list level, for talking rather than "doing". A discussion has a category (General, Ideas, Q&A, Show & tell), a title and a markdown body, then replies. Discussions have no status, labels or assignees. (Comments on a specific item are about edits and live inside a suggestion — see above.)

Stars & star folders

Stars are bookmarks plus a popularity signal. Organize starred lists into folders (like GitHub Lists) from your stars page.

Watching & notifications

Watch a list (choosing a level) and follow people to see their activity in your feed; notifications arrive in the bell menu, optionally by email and browser push. The full detail is in Notifications & subscriptions.

Collaborators

The owner can invite collaborators with write access: they can edit the list and push to it via git without going through suggestions.

List health panel

On your My lists page each list gets a traffic-light status: red — needs attention (open suggestions and issues, broken links found by the gardener), yellow — has activity (fresh forks, stars, discussions), green — all quiet. Sorting by "what hurts now" helps you run dozens of lists without losing track of the ones waiting on you.