Skip to content

Contribution Record

Sample Contribution Record

CompletedPrivateFictional

Invitation reliability program

Illustrative example — fictional data.

This is not a participant outcome or a GitHub verification. It uses the same Contribution Record layout participants see.

Sample contributor completed Invitation reliability program

The maintainer confirmed completion. The record below preserves accepted milestones and their submitted evidence history.

Completed Jun 12, 2026

Accepted milestones

  1. Distinguish expired and already-used invitation links

    Acceptance criteria: Expired and already-used invitation links show distinct states, retries stay safe, and regression tests cover both.

    Reviewed by Sample maintainer on May 23, 2026.

    Acceptance context: The first review asked for an already-used-link regression test and a note on the expected state. The revision added both, so the bounded task was accepted.

    • Earlier submission 1

      First submission: distinct expired-link state with tests.

      Earlier submitted revision; not the accepted submission

    • Accepted work 2

      Added the already-used-link regression test and explained why later visits show the completed invitation state.

      Submission present when this milestone was accepted

  2. Agree the retry edge cases before coding

    Acceptance criteria: Duplicate, expired, and interrupted requests are listed and agreed before the retry path is changed.

    Reviewed by Sample maintainer on Jun 8, 2026.

    Acceptance context: The edge cases were agreed before coding, and the change matched them.

    • Accepted work 1

      Edge-case list agreed in review, then the retry change with tests.

      Submission present when this milestone was accepted

Maintainer confirmation

The maintainer confirmed that the required milestones were accepted.

Both required milestones were accepted. The contributor applied review feedback within the agreed scope.

Agreed program context

Development goal
Handle edge cases in a production invitation flow, with tests that prove them.
AI policy
AI use allowed with disclosure
Maintainer
Sample maintainer
Planned reviewer
Sample maintainer

These are historical terms frozen when the program started. They do not assert authorship, competence, or the current state of linked work.

Developer reflection

Writing the edge cases down before coding made the second review much shorter.