Skip to content

Conversation

@cmeesters
Copy link
Member

@cmeesters cmeesters commented May 14, 2025

Summary by CodeRabbit

  • Chores
    • Updated release announcement workflow to use the release tag name instead of the pull request title when posting to Mastodon.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 14, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The GitHub Actions workflow for announcing releases on Mastodon was updated to change the input parameter for the announcement message. Instead of using the pull request title, the workflow now uses the release tag name from the event payload as the source for the pr-title input.

Changes

File(s) Change Summary
.github/workflows/announce-release.yml Updated the workflow to use github.event.release.tag_name instead of github.event.pull_request.title for the pr-title input in the Mastodon announcement step.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Release Event
    participant GitHub Actions Workflow
    participant Mastodon

    GitHub Release Event->>GitHub Actions Workflow: Trigger workflow on release
    GitHub Actions Workflow->>GitHub Actions Workflow: Extract release tag name as pr-title
    GitHub Actions Workflow->>Mastodon: Post announcement using release tag name
Loading

Possibly related PRs

  • fix: mastodonbot #187: Also modifies the Mastodon announcement workflow to use the release tag name instead of the PR title.
  • fix: added pr title #276: Changes the same input parameter in the workflow file, indicating a direct connection.
  • fix: trying syntax fix #235: Alters the workflow to change the source of information for the Mastodon announcement, focusing on event payload fields.

Suggested reviewers

  • dlaehnemann

Poem

A tag is born, the bunny cheers,
Announcing releases for all to hear!
No more titles from PR's past,
The tag name now is posted fast.
🐰🎉
Code hops forward, swift and neat—
Mastodon updates can't be beat!

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2404f69 and 0ad14ab.

📒 Files selected for processing (1)
  • .github/workflows/announce-release.yml (1 hunks)

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.

❤️ Share
🪧 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.

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.

@cmeesters cmeesters merged commit eae7276 into main May 14, 2025
2 of 4 checks passed
@cmeesters cmeesters deleted the fix/pr_title branch May 14, 2025 16:55
cmeesters pushed a commit that referenced this pull request May 14, 2025
🤖 I have created a release *beep* *boop*
---


##
[1.2.11](v1.2.10...v1.2.11)
(2025-05-14)


### Bug Fixes

* pr title from tag
([#281](#281))
([eae7276](eae7276))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated the changelog with a new entry for version 1.2.11, detailing a
recent bug fix.
  - Bumped the package version to 1.2.11.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@coderabbitai coderabbitai bot mentioned this pull request May 16, 2025
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