Catana Documentation
  • 🐱Overview
    • Introduction
    • Installation
  • 📖Core concepts
    • Regular and expiring TODOs
    • Assigning TODOs
    • Create, update and delete
    • Validation
    • Ignored TODOs
  • 🔔Triggers
    • Overview
    • Date
    • GitHub Issue closed
    • GitHub Pull Request closed
    • Ruby Gem released
    • Ruby Gem upgraded
    • Ruby Version released
    • Ruby Version upgraded
  • 🤖Commands
    • Overview
    • Done
    • Bump
    • Link
  • 🔗Grouped TODOs
    • Overview
  • ⚙️Configuration
    • Open GitHub issues
    • Enforce expiring TODOs
    • Rules
    • Exclusion list
Powered by GitBook
On this page

Was this helpful?

  1. Commands

Bump

PreviousDoneNextLink

Last updated 8 months ago

Was this helpful?

The Bump command is used to edit and follow up on .

When to use it

The bump command can be compared with the 'snooze' feature on an alarm clock. When it rings, you either wake up right away or snooze it to ring again later. Snoozing and sleeping a bit more is the norm.

Similarly, when a TODO expires, it's completely acceptable to push it back to a later date because you have other priorities.

Leaving an expired TODO untouched is a bad practice for two reasons:

  1. It confuses your team members as to why a TODO expired but still remained in the codebase.

  2. Even if there is a ticket open, it's likely you'll forget about it unless you get reminded again.

Command

➡️ @catanacorpbump[argument]

Catana will edit the TODO in the repository, open a Pull Request, and assign it to the user who invoked the command.

Arguments

This command accepts arguments such as:

  • @catanacorpbumptomorrow

  • @catanacorpbumpnext week

  • @catanacorpbumpnext month

  • @catanacorpbump2023-06-18 (Where 2023-06-18 can be any date)

Once the Pull Request is merged the Todo Item record in Catana's database will be .

🤖
updated
expiring TODOs