Ship from issues

Get started for free

Tasks for this goal

  1. Turn an issue into a pull request

    A pull request that passes your tests and linter, checked by a second agent's review before anyone merges it.

  2. Fix a production error

    A pull request with a test that reproduces the error and the fix that makes it pass.

  3. Update dependencies

    A pull request with current dependencies and the code adapted to their breaking changes.

  4. Write release notes

    Release notes for the changes merged since your last release, added to your changelog in a reviewed pull request.

  5. Clear the small tickets in your backlog

    One reviewed pull request per ticket, with checks passing.

  6. Review a teammate's change before it ships

    A list of problems with concrete examples.

  7. Add tests before anyone touches old code

    Tests that record how the code behaves today, all passing.

  8. Find out why a test fails only sometimes

    The cause of the failures, with the runs that prove it and a fix to try.

  9. Add logging around a failure you can't reproduce

    A change that logs the values the failure depends on, with personal data masked.

  10. Delete dead code

    One reviewed pull request that deletes the code your product no longer calls.

  11. Document a part of your code

    Docs that match what the code does.

See one in action

Search Acme

support

2

  1. Fabian

    @devboxes can you pick up DEV-31? enterprise customers get payment reminders before their grace period is over

  2. devboxes APP

    Looked at 4 sources
    1. Jira Read DEV-31 and its comments
    2. GitHub Opened src/dunning/schedule.ts
    3. GitHub Found gracePeriodDays on customers
    4. Jira Moved DEV-31 to In Review

    #52 is up. The first reminder now waits out the customer's grace period, which was already on the customer record. Checks pass and DEV-31 is in review.

    Jira

    DEV-31 Payment reminders ignore the enterprise grace period

    In Review Dunning

    GitHub

    #52 Respect the contract's grace period before reminding

    Open devboxes/dev-31 3 checks passed

    Opened #52

  3. Fabian

    @devboxes Nina wants the grace period on #52 in business days, that's how the contracts are written

  4. devboxes APP

    Looked at 3 sources
    1. GitHub Read Nina's comment on #52
    2. GitHub Found the reminders' calendar
    3. Terminal Ran the tests

    Done. #52 now counts business days with the same calendar the reminders use, and there's a test for a due date right before a weekend.

    Updated #52

Ask devboxes to ship from issues

Get started for free