chore: remove release drafter configuration and workflow - #64
Conversation
Reviewer's GuideThe PR simplifies and hardens the Release Drafter GitHub Actions setup by removing the separate configuration file, inlining fixed prerelease and release settings in the workflow, updating event triggers, and adding a dedicated prerelease job while bumping the Release Drafter action version. Flow diagram for the updated Release Drafter workflowflowchart LR
subgraph GitHubEvents
push_main["push to main"]
pull_request_events["pull_request (opened/edited/etc.)"]
end
push_main --> update_release_draft
pull_request_events --> update_prerelease_draft
subgraph WorkflowJobs
update_prerelease_draft["job update_prerelease_draft\nprerelease: true\nidentifier: rc"]
update_release_draft["job update_release_draft\nprerelease: false"]
end
subgraph ReleaseDrafter
release_drafter_action["release-drafter@v7.7.0\ninline config"]
end
update_prerelease_draft --> release_drafter_action
update_release_draft --> release_drafter_action
File-Level Changes
Assessment against linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Warning Review limit reached
Next review available in: 18 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- The PR title suggests fully removing Release Drafter, but the workflow still uses
release-drafter; if the intent is to stop using it, consider deleting the workflow rather than updating and version-bumping it. - With
.github/release-drafter.ymlremoved, the Release Drafter action will fall back to its defaults; if you still need customized release notes behavior, consider retaining a minimal configuration file instead of deleting it outright.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The PR title suggests fully removing Release Drafter, but the workflow still uses `release-drafter`; if the intent is to stop using it, consider deleting the workflow rather than updating and version-bumping it.
- With `.github/release-drafter.yml` removed, the Release Drafter action will fall back to its defaults; if you still need customized release notes behavior, consider retaining a minimal configuration file instead of deleting it outright.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| branches: | ||
| - main | ||
| pull_request_target: | ||
| pull_request: |
There was a problem hiding this comment.
WARNING: Changing pull_request_target to pull_request breaks the workflow for PRs from forks
The pull_request event provides a read-only GITHUB_TOKEN for PRs from forks, but this workflow needs contents: write and pull-requests: write permissions to update release drafts and PR comments. Fork PRs will fail silently or with permission errors. Consider retaining pull_request_target or adding a separate pull_request job with reduced permissions if fork support is needed.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| cancel-in-progress: ${{ github.ref != 'refs/heads/main' && github.ref_type != 'tag' }} | ||
|
|
||
| jobs: | ||
| update_prerelease_draft: |
There was a problem hiding this comment.
WARNING: Missing if: conditions on jobs causes both to run for all events
Neither update_prerelease_draft nor update_release_draft has an if: condition, so both jobs execute for every trigger event (push to main, all PR event types). For push events, this creates both a release draft and a prerelease draft simultaneously, which may conflict. For PR events, both jobs also run even though only the prerelease draft may be intended. Add if: github.event_name == 'pull_request' to update_prerelease_draft and if: github.event_name == 'push' to update_release_draft.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Reviewed by step-3.7-flash · Input: 64K · Output: 13.2K · Cached: 201.9K |
Closes #63
Summary by Sourcery
Streamline Release Drafter automation for releases and prereleases triggered by pushes and pull requests.
Build: