Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

cli countdown support

Open
#405 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Start by comparing the TUI's countdown handling with the CLI implementation of hey event day, especially its --json output. Confirm the expected countdown fields from the TUI, then make the CLI expose them and verify that hey event day --json includes countdown attributes without confusing them with reminders.

Written by the indexing model from the issue text.

Description

Needs API

Though countdowns are exposed through the TUI, I can't find that information in the CLI:


# 5 events today
❯ hey event day --count
5

# no 'countdown' attributes in the json
❯ hey event day --json | grep countdown


# there is a reminders key, but that's different in hey to countdowns
❯ hey event day --json | grep reminder
        "reminders": [
        "reminders_label": "30 minutes before",
      "reminders": [
      "reminders_label": "30 minutes before",
        "reminders": [
        "reminders_label": "30 minutes before",
      "reminders": [
      "reminders_label": "30 minutes before",
        "reminders": [
        "reminders_label": "30 minutes before",
      "reminders": [
      "reminders_label": "30 minutes before",
      "reminders": [
      "reminders_label": "30 minutes before",
      "reminders": [
      "reminders_label": "30 minutes before",

The hey cli is a terrific addition to my organisation, even without this, thanks so much folks!

Dominant language
Go
Stars
409
Forks
49
Avg merge
1d 6h
Merged PRs (30d)
81

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from basecamp/hey-cli

All issues in basecamp/hey-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.