leereilly / leereilly/gh-commit-crawl

Found the Easter egg!

Open
#2 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
13
Forks
1
PR merge metrics
No merged PRs in 30d

Description

What problem or experience are you solving for?

Thanks for the t-shirt 😃

What would you like to see happen?

Another cool Easter egg next year

Anything you've already considered or tried?

No response

Are you interested in contributing this?
  • I'd be happy to send a PR.

Contributor guide

Open the contributing guide

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.

Research direction

The issue does not identify a file, entry point, or specific Easter egg to implement. Start by reviewing the Go GitHub CLI extension and clarifying the desired experience with the maintainers; done criteria need to be agreed before implementation can begin.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.