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
  • Usage with a syntax
  • Authorization
  • Usage when detected automatically

Was this helpful?

  1. Triggers

GitHub Issue closed

PreviousDateNextGitHub Pull Request closed

Last updated 5 months ago

Was this helpful?

Use the GitHub issue closed trigger to expire a TODO when a GitHub issue is closed.

Usage with a syntax

➡️ TODO(on:issue_closed('rails', 'rails', 631))

Authorization

This trigger can be used to monitor issues on any public repositories or private repositories belonging to the same organization the TODO is introduced.

Examples

Expire a TODO when the issue #631 from the Rails repository is closed

➡️ TODO(on:issue_closed('rails', 'rails', 631))

Usage when detected automatically

When the repository or organisation is not specified, Catana will assume you are referring to an issue in the current repository.

Examples

TODO: Reuse the calendar component once we fix #754 Equivalent to: issue_closed('org', 'repo', 754)

TODO: Awaiting for kubernetes/k8s.io#7314 Equivalent to: issue_closed('kubernetes', 'k8s.io', 7314)

TODO: Do something if https://github.com/github-linguist/linguist/pulls/344 is resolved Equivalent to: issue_closed('github-linguist', 'linguist', 344)

🔔