Announcements

Day 17: Changelog Generator โ€” Now supports private repos

Transform commit history into professional changelogs with private repo support. Use GitHub tokens to access private repositories, control scope (1/5/10 commits), and generate Keep a Changelog format release notes with AI.

3 min read
Day 17 Changelog Generator with private repo support and scope control

Day 17 unlocks the Changelog Generator with major updates: private repository access via GitHub tokens, precise scope control (1/5/10 commits), and enhanced privacy controls.

What's new in Day 17

๐Ÿ” Private Repository Support

Access your private repos securely using GitHub Personal Access Tokens (PAT). Your token stays client-side only โ€” we never send it to our servers. Fetch commits directly from GitHub using your credentials.

๐ŸŽฏ Scope Control

Choose exactly how many commits to include: latest 1, 5, or 10 commits. Perfect for focused release notes or quick changelog updates. The UI and DeepSeek both honor your selection.

๐Ÿ“Š Token Tracking

See your daily token usage in real-time. Each account gets 15,000 free tokens per day (resets at midnight UTC). Most changelog generations use 500-2,000 tokens depending on commit count.

How to use private repo access

Step 1: Create a GitHub Token

  1. Visit GitHub Settings โ†’ Tokens
  2. Click "Generate new token (classic)" or "Fine-grained tokens"
  3. For classic: Select repo scope (full control of private repos)
  4. For fine-grained: Select Contents: Read-only for specific repos
  5. Copy your token (starts with ghp_ or github_pat_)

Step 2: Use Your Token

  1. Paste your private repo URL (e.g., github.com/yourname/private-repo)
  2. Enter your GitHub token in the password field
  3. Wait for validation (green badge = valid, red = invalid)
  4. Select scope (latest 1, 5, or 10 commits)
  5. Click "Generate Changelog"

Step 3: Authorize SSO (if needed)

If your org requires SSO authorization, click "Authorize" next to your org name in the token settings. This grants your token access to org repos.

Tips for best results

  • Use conventional commits โ€” feat:, fix:, docs: for automatic categorization
  • Choose the right scope โ€” Latest 1 for hotfixes, 5-10 for minor releases
  • Check token limits โ€” Track remaining tokens in the top-right corner
  • Revoke tokens after use โ€” Delete tokens you no longer need in GitHub settings
  • Test with public repos first โ€” Verify the tool works before using private repos

Privacy & Security

Your GitHub token is processed entirely client-side. We fetch commits directly from GitHub's API using your token, then send only the commit data to DeepSeek for formatting. Your token never touches our servers.

Daily token limits prevent abuse and keep costs sustainable. Tokens reset automatically at midnight UTC. No payment required.

Try it now

Visit /day/17 to generate professional changelogs from public or private repos. Create a GitHub token, paste your repo URL, and watch your commits transform into release notes.

Ship faster with polished changelogs. ๐Ÿš€๐Ÿ“ฐ