Skip to content

ci: cleanup draft pr tags#1097

Merged
alandtse merged 1 commit into
community-shaders:devfrom
alandtse:pr_cleanup
May 27, 2025
Merged

ci: cleanup draft pr tags#1097
alandtse merged 1 commit into
community-shaders:devfrom
alandtse:pr_cleanup

Conversation

@alandtse
Copy link
Copy Markdown
Contributor

@alandtse alandtse commented May 27, 2025

Summary by CodeRabbit

  • Chores
    • Improved handling of prerelease tag cleanup for pull requests, with more accurate checks for PR status and clearer output messages.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 27, 2025

Walkthrough

The pull request updates the GitHub Actions workflow responsible for cleaning up prerelease tags associated with pull requests. The logic for determining when to delete a prerelease tag is improved by checking both the PR state and draft status, and fallback Git commands for tag deletion are removed.

Changes

File(s) Change Summary
.github/workflows/cleanup-pr-releases.yaml Refined PR status check to include draft status, improved tag deletion logic, removed fallback Git commands, and updated output messages.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow
    participant GitHubAPI

    Workflow->>GitHubAPI: Query PR state and draft status for each prerelease tag
    alt PR not found
        Workflow->>Workflow: Delete prerelease tag
    else PR not open or is draft
        Workflow->>Workflow: Delete prerelease tag
    else PR open and not draft
        Workflow->>Workflow: Keep prerelease tag
    end
Loading

Possibly related PRs

Suggested reviewers

  • jiayev

Poem

In the warren of tags, I hop with glee,
Pruning the drafts, as tidy as can be.
No more fallback tricks, just clear, concise checks—
Open and ready? The tag still decks.
For closed or draft, I sweep them away,
Keeping the garden neat, every day!
🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (3)
.github/workflows/cleanup-pr-releases.yaml (3)

36-39: Refactor PR existence check for robustness
Relying on string comparison against "NOT_FOUND" can break if the output format changes. Instead, use the exit status of gh pr view to detect missing PRs:

- if [[ "$pr_info" == "NOT_FOUND" ]]; then
-   echo "PR #$pr_number not found. Deleting prerelease tag $tag"
-   gh release delete "$tag" --yes --cleanup-tag
-   continue
- fi
+ if ! pr_info=$(gh pr view "$pr_number" --json state,isDraft 2>/dev/null); then
+   echo "PR #$pr_number not found. Deleting prerelease tag $tag"
+   gh release delete "$tag" --yes --cleanup-tag
+   continue
+ fi

42-43: Use here-string for JSON parsing
To preserve JSON formatting and avoid potential whitespace issues, prefer:

pr_state=$(jq -r '.state' <<< "$pr_info")
pr_draft=$(jq -r '.isDraft' <<< "$pr_info")

over piping through echo.


45-46: Fix conditional draft label in log
${pr_draft:+ (draft)} expands for any non-empty value, causing "(draft)" to appear even when pr_draft is "false". Introduce an explicit check:

- echo "PR #$pr_number is $pr_state${pr_draft:+ (draft)}. Deleting prerelease tag $tag"
+ draft_label=""
+ if [[ "$pr_draft" == "true" ]]; then
+   draft_label=" (draft)"
+ fi
+ echo "PR #$pr_number is $pr_state$draft_label. Deleting prerelease tag $tag"
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4d417dd and 1946dcd.

📒 Files selected for processing (1)
  • .github/workflows/cleanup-pr-releases.yaml (1 hunks)
🔇 Additional comments (2)
.github/workflows/cleanup-pr-releases.yaml (2)

35-35: Ensure GH CLI supports isDraft field
The --json state,isDraft flag requires a recent GH CLI. Verify the CI environment uses GH CLI ≥ 2.22.0 or implement fallback logic if isDraft isn’t supported.


49-49: Approve retention logic for active PRs
The else branch correctly retains tags for open, non-draft PRs with a clear log message.

@alandtse alandtse merged commit da8eeda into community-shaders:dev May 27, 2025
6 checks passed
alandtse added a commit to alandtse/open-shaders that referenced this pull request Jul 20, 2025
@coderabbitai coderabbitai Bot mentioned this pull request Jul 28, 2025
@alandtse alandtse deleted the pr_cleanup branch December 24, 2025 19:48
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