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(workflow): fix set-env job (checkout + token) #309

Merged
merged 1 commit into from
Nov 13, 2024
Merged

Conversation

ccamel
Copy link
Member

@ccamel ccamel commented Nov 13, 2024

Self explanatory.

(same than axone-protocol/axoned#814)

Summary by CodeRabbit

  • New Features

    • Enhanced release notification process with improved GitHub API interaction.
    • Added environment variable GH_TOKEN for secure authentication during release operations.
  • Improvements

    • Updated logic for determining release tags to utilize the new token.
    • Conditional execution for documentation updates based on event triggers.

@ccamel ccamel self-assigned this Nov 13, 2024
Copy link
Contributor

coderabbitai bot commented Nov 13, 2024

Walkthrough

The pull request modifies the .github/workflows/notify-release.yml workflow file to enhance the release notification process. Key updates include adding a repository checkout step, introducing the GH_TOKEN environment variable for GitHub CLI authentication, and updating the notify-github-discussion job to use this token for fetching changelogs. The update-docs job is now conditionally executed based on the event type, maintaining its original functionality while improving context awareness for the release process.

Changes

File Change Summary
.github/workflows/notify-release.yml - Added repository checkout step using actions/checkout@v4.
- Introduced GH_TOKEN sourced from ${{ secrets.OPS_TOKEN }} for GitHub CLI authentication.
- Updated logic to fetch release tag using GH_TOKEN.
- Modified notify-github-discussion job to include GH_TOKEN and other environment variables.
- Made update-docs job conditionally executed based on event name.

Possibly related PRs

  • Ci/notify discussions release #302: The changes in this PR also modify the .github/workflows/notify-release.yml file, specifically enhancing the release notification process and introducing the notify-github-discussion job, which is directly related to the updates made in the main PR.

Suggested reviewers

  • bdeneux
  • amimart

🐰 In the meadow where bunnies play,
A workflow blooms in a brand-new way.
With tokens and checks, it hops along,
To notify all with a joyful song!
So raise your ears and give a cheer,
For seamless releases are finally here! 🥕✨


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>, please review it.
    • 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 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 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 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 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
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

🧹 Outside diff range and nitpick comments (3)
.github/workflows/notify-release.yml (3)

Line range hint 38-77: Consider adding error handling for discussion creation

The discussion creation implementation looks good, but consider adding error handling for cases where the discussion creation might fail (e.g., rate limits, network issues, or missing permissions).

Add a step to verify the discussion was created:

      - name: Create an announcement discussion for release
        uses: abirismyname/[email protected]
+       id: create-discussion
        with:
          title: 🎉 ${{ needs.set-env.outputs.repo_name }} ${{ needs.set-env.outputs.tag }} released!
          # ... rest of the config ...

+     - name: Verify discussion creation
+       if: steps.create-discussion.outputs.discussion-id == ''
+       run: |
+         echo "::error::Failed to create discussion"
+         exit 1

Line range hint 79-99: Consider making the docs API URL configurable

The workflow URL is currently hardcoded. Consider moving it to a repository variable for better maintainability and reusability.

Example improvement:

       with:
-         url: "https://api.github.com/repos/axone-protocol/docs/actions/workflows/39152549/dispatches"
+         url: ${{ vars.DOCS_UPDATE_WORKFLOW_URL }}
          method: "POST"
🧰 Tools
🪛 actionlint

23-23: shellcheck reported issue in this script: SC2086:info:6:20: Double quote to prevent globbing and word splitting

(shellcheck)


23-23: shellcheck reported issue in this script: SC2295:info:8:31: Expansions inside ${..} need to be quoted separately, otherwise they match as patterns

(shellcheck)


23-23: shellcheck reported issue in this script: SC2086:info:9:32: Double quote to prevent globbing and word splitting

(shellcheck)


Line range hint 1-99: Well-structured workflow with proper separation of concerns

The workflow is well-organized with clear job separation and proper use of:

  • Job dependencies and outputs
  • Environment variables and secrets
  • Conditional execution
  • GitHub Actions best practices

Consider adding timeouts to the jobs to prevent hanging in case of issues:

  set-env:
    runs-on: ubuntu-22.04
+   timeout-minutes: 5
    outputs:
      tag: ${{ steps.set-env.outputs.tag }}
🧰 Tools
🪛 actionlint

23-23: shellcheck reported issue in this script: SC2086:info:6:20: Double quote to prevent globbing and word splitting

(shellcheck)


23-23: shellcheck reported issue in this script: SC2295:info:8:31: Expansions inside ${..} need to be quoted separately, otherwise they match as patterns

(shellcheck)


23-23: shellcheck reported issue in this script: SC2086:info:9:32: Double quote to prevent globbing and word splitting

(shellcheck)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2d78350 and 9975052.

📒 Files selected for processing (1)
  • .github/workflows/notify-release.yml (2 hunks)
🔇 Additional comments (1)
.github/workflows/notify-release.yml (1)

18-20: LGTM! Verify OPS_TOKEN permissions

The addition of the checkout step and GH_TOKEN environment variable are correct and necessary changes. The checkout step is required to access repository content, and the GH_TOKEN is needed for GitHub CLI operations.

Let's verify the token permissions:

Also applies to: 35-35

@ccamel ccamel merged commit b7a83f0 into main Nov 13, 2024
11 checks passed
@ccamel ccamel deleted the ci/fix-notify-release branch November 13, 2024 12:09
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