Skip to content

Conversation

@waleedlatif1
Copy link
Collaborator

Summary

added changelog and gh action to auto-release every time we push to main, will automatically release and update the changelog page so users and subscribers can keep track of the updates

Type of Change

  • Documentation

Testing

Manually

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

Screenshot 2025-09-22 at 9 19 13 PM

@vercel
Copy link

vercel bot commented Sep 23, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Sep 23, 2025 4:32am
sim Canceled Canceled Sep 23, 2025 4:32am

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Greptile Summary

This PR implements a changelog feature that fetches release data from GitHub API and displays it on a dedicated page. The implementation includes a release automation script, RSS feed support, and necessary CSP updates to allow GitHub API calls.

Key additions:

  • Release automation script (scripts/create-single-release.ts) that generates GitHub releases with categorized commit messages
  • Changelog page with timeline view of releases fetched from GitHub API
  • RSS feed endpoint (/changelog.xml) for programmatic access to releases
  • Enhanced Avatar component with status indicators
  • CSP policy updates to allow connections to GitHub domains

Areas of concern:

  • The PR description mentions "GitHub action to auto-release" but no workflow files were added - only a manual release script
  • GitHub API calls lack authentication which may cause rate limiting issues
  • Direct API calls in components without proper error boundaries

Confidence score: 3/5

  • This PR is moderately safe but has implementation inconsistencies that need attention
  • Score reflects missing GitHub automation workflow despite claims, potential rate limiting issues with unauthenticated API calls, and the discrepancy between PR description and actual implementation
  • Pay close attention to the GitHub API integration in changelog components and verify the auto-release workflow implementation

13 files reviewed, 3 comments

Edit Code Review Bot Settings | Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants