Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: check if release notes are properly created #1122

Merged
merged 5 commits into from
Jul 4, 2024
Merged

Conversation

Czaki
Copy link
Collaborator

@Czaki Czaki commented Jul 4, 2024

Summary by CodeRabbit

  • Chores
    • Implemented a new step in the GitHub release workflow to verify the content of release notes before creating a release.

@Czaki Czaki added this to the 0.15.3 milestone Jul 4, 2024
Copy link
Contributor

coderabbitai bot commented Jul 4, 2024

Walkthrough

The recent updates to the GitHub workflow introduce a new step that checks the release notes content before creating a release. This enhancement ensures that all releases have properly vetted documentation, improving release quality without altering any exported or public entities.

Changes

Files Change Summary
.github/workflows/make_release.yml Added a step to check the release notes content before creating a release in the workflow.

Poem

In the code's quiet dance, a step anew,
To check release notes, through and through.
Ensuring all is right, before we take flight,
Our workflow enhanced, shining bright!
🎨✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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
Contributor

sourcery-ai bot commented Jul 4, 2024

🧙 Sourcery has finished reviewing your pull request!


Tips
  • Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
  • Continue your discussion with Sourcery by replying directly to review comments.
  • You can change your review settings at any time by accessing your dashboard:
    • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
    • Change the review language;
  • You can always contact us if you have any questions or feedback.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We've reviewed this pull request using the Sourcery rules engine. If you would also like our AI-powered code review then let us know.

Copy link
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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4162135 and 59503b2.

Files selected for processing (1)
  • .github/workflows/make_release.yml (1 hunks)
Additional comments not posted (2)
.github/workflows/make_release.yml (2)

Line range hint 116-126:
LGTM!

The configuration for creating a release using softprops/action-gh-release@v2 looks good.


Line range hint 127-129:
LGTM!

The configuration for publishing package distributions to PyPI using pypa/gh-action-pypi-publish@release/v1 looks good.

Comment on lines 114 to 115
- name: check release notes
run: echo ${{ steps.release_notes.outputs.contents }}
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider validating the release notes content.

While echoing the release notes is useful, adding a validation check to ensure the content meets certain criteria (e.g., non-empty, follows a specific format) would be beneficial.

-  run: echo ${{ steps.release_notes.outputs.contents }}
+  run: |
+    RELEASE_NOTES=${{ steps.release_notes.outputs.contents }}
+    if [ -z "$RELEASE_NOTES" ]; then
+      echo "Release notes are empty. Aborting release."
+      exit 1
+    fi
+    echo "$RELEASE_NOTES"
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: check release notes
run: echo ${{ steps.release_notes.outputs.contents }}
- name: check release notes
run: |
RELEASE_NOTES=${{ steps.release_notes.outputs.contents }}
if [ -z "$RELEASE_NOTES" ]; then
echo "Release notes are empty. Aborting release."
exit 1
fi
echo "$RELEASE_NOTES"

Copy link
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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 59503b2 and 7586660.

Files selected for processing (1)
  • .github/workflows/make_release.yml (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/make_release.yml

Copy link
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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7586660 and ed90f21.

Files selected for processing (1)
  • .github/workflows/make_release.yml (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/make_release.yml

Copy link

sonarqubecloud bot commented Jul 4, 2024

Copy link
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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ed90f21 and 3557ccb.

Files selected for processing (1)
  • .github/workflows/make_release.yml (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/make_release.yml

@Czaki Czaki merged commit 5854740 into develop Jul 4, 2024
57 checks passed
@Czaki Czaki deleted the fix_release_notes branch July 4, 2024 22:38
Copy link

codecov bot commented Oct 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.91%. Comparing base (4162135) to head (3557ccb).
Report is 81 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1122   +/-   ##
========================================
  Coverage    92.91%   92.91%           
========================================
  Files          205      205           
  Lines        32519    32519           
========================================
  Hits         30215    30215           
  Misses        2304     2304           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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.

1 participant