When a linked pull request merges, Grove reads the code and checks each of the project's outcomes. Your product lead uses what Grove finds to decide what to try, and what to mark done.
This needs the Grove GitHub app connected to your workspace.
When Grove reads the code
On merge. Grove reads the code when a linked pull request merges. It doesn't read open pull requests.
Again on later merges. If a later merge changes what Grove would find, Grove reads again.
Then it stops. Once Grove finds an outcome done, it doesn't read that outcome again.
Linking and checking your claims' quotes happen each time the pull request changes.
How Grove reads it
Grove reads the code as it stands after the merge, from the user's point of view.
It doesn't see your claim. Grove reads without knowing what you said the pull request does.
It doesn't count messages. Commit messages and code comments aren't evidence.
It rates each outcome. An outcome counts as done only when Grove is fairly sure the code delivers it.
What the tags mean
Tag | When |
Nothing linked | You didn't claim the outcome, and nothing that changes it has merged. |
Building | Work on the outcome is linked or claimed, and Grove hasn't found it done. |
Ready for review | Grove read the code and found the outcome done, whatever was claimed. |
Needs you | You claimed |
Done | Your product lead ticked the outcome. This overrides every other tag. |
If Grove hasn't finished reading 10 minutes after a merge, the outcome shows your claim until it does.
Where your pull requests show
On the project's Scope, below the outcomes:
Pull requests that couldn't be matched: merged pull requests that match no outcome, and open ones that name an outcome the project doesn't have.
Grove is still checking these: merged pull requests Grove is still reading. They move to an outcome, or to the list above, on their own.
Your product lead can click any outcome's tag to see the pull requests behind it, and what Grove found.
If Grove disagrees with you
Needs you means Grove and you disagree. Grove can't settle that. Your product lead tries the work and decides.
If your claim's quote was wrong, fix the claims block.
If the work isn't finished, keep building, and claim
advancesuntil it is.If you think the work is done, say so in a thread on the project, or reply to your product lead's thread.
Only a person marks an outcome Done, or a project Built. Grove never does.