Docs · Issues
Issues
An issue is a piece of work someone wants done, written for a person. In Anvil it's also a brief: a thread can start on it as it stands.
Filing
Write the title and as much as you know. From a terminal:
anvil issue new --project harbor "Upload retries give up after one 503" \ --body-file notes.md --label bug
Issues also arrive on their own: a check that fails on main twice in a row files one, a review comment can be turned into one, and users of the app you ship report from inside it, with a screenshot, the version and what they were doing.
Triage
The project's Lead reads each new issue. It finds the code it's about, labels it, links what's related, asks the person who filed it anything it can't tell, and writes down what it would do. Triage changes nothing in the code.
Starting a thread
Say go to the Lead's plan, or start a thread yourself:
anvil thread start --issue harbor#212 --on auto
The thread gets the issue, the Lead's notes and the project's documents as its brief, and works on a branch named for it. The issue's timeline shows the thread working, its commits, the change it opens and the checks on it.
Closing
A change made for an issue closes it when it merges, and the people following the issue are told which release it ships in. Close an issue by hand with a note, and the note goes to them instead.
Tasks
Work too big for one change is a task, with the issues and changes under it. Ask the Lead to split a task and it starts a thread for each part, keeps their branches in step, and reports on the task as a whole.