Skip to content

fix/ee release pipelines #1926

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

Merged
merged 2 commits into from
Mar 27, 2025
Merged

fix/ee release pipelines #1926

merged 2 commits into from
Mar 27, 2025

Conversation

motatoes
Copy link
Contributor

@motatoes motatoes commented Mar 27, 2025

  • improve path name
  • update slack provider

Summary by CodeRabbit

  • Chores
    • Updated internal release configuration to align with a revised directory structure.
  • Bug Fixes
    • Enhanced error messaging for drift notifications, now providing clear guidance on required environment variable settings.

Copy link
Contributor

coderabbitai bot commented Mar 27, 2025

Walkthrough

The pull request updates the EE CLI release workflow by modifying the project_path parameter to reflect its new directory location. Additionally, it refines the error message in the drift provider to clearly indicate that the Slack notification URL must be specified using the INPUT_DRIFT_DETECTION_SLACK_NOTIFICATION_URL environment variable.

Changes

File(s) Change Summary
.github/.../ee_cli_release.yml Updated project_path from ./cli/cmd/digger to ./ee/cli/cmd/digger in the GitHub Actions release workflow.
cli/.../Provider.go Modified error message to specify the required environment variable for Slack notifications in drift mode.

Possibly related PRs

Poem

In the realm of code where bunnies dwell,
I hopped along a brand new trail so well,
Paths realigned and errors clarified,
My whiskers twitch with joyful pride,
For in our code garden, smooth fixes swell! 🐇✨

Happy hops and bug-free loops!

✨ Finishing Touches
  • 📝 Generate Docstrings

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.
    • 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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@motatoes motatoes merged commit 28a8ecd into develop Mar 27, 2025
77 of 78 checks passed
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
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e7504dc and 22ce7a4.

📒 Files selected for processing (2)
  • .github/workflows/ee_cli_release.yml (1 hunks)
  • cli/pkg/drift/Provider.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Build
  • GitHub Check: Build
🔇 Additional comments (1)
.github/workflows/ee_cli_release.yml (1)

33-33:

✅ Verification successful

Path updated to reflect the new EE CLI location.

The change correctly points to the new project path for the Enterprise Edition CLI. This is consistent with the PR objective to improve the path name.


🏁 Script executed:

#!/bin/bash
# Check if the new path structure exists in the repository
if [ -d "./ee/cli/cmd/digger" ]; then
  echo "✅ The new path './ee/cli/cmd/digger' exists."
else
  echo "❌ Warning: The path './ee/cli/cmd/digger' doesn't exist in the repository."
  echo "This might cause the workflow to fail."
fi

Length of output: 137


Verified: EE CLI Path Update is Correct

File: .github/workflows/ee_cli_release.yml, line 33
The updated project path now correctly points to ./ee/cli/cmd/digger, which has been confirmed to exist. This change aligns with the PR objective to update the path for the Enterprise Edition CLI.

@@ -19,7 +19,7 @@ func (d DriftNotificationProviderBasic) Get(prService ci.PullRequestService) (co
if slackNotificationUrl != "" {
notification = SlackNotification{slackNotificationUrl}
} else {
return nil, fmt.Errorf("could not identify drift mode, please specify slack or github")
return nil, fmt.Errorf("could not identify drift mode, please specify slack using env variable INPUT_DRIFT_DETECTION_SLACK_NOTIFICATION_URL")
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Improved error message with specific environment variable.

The error message has been updated to provide clearer guidance on how to configure the Slack notification URL using a specific environment variable. This change enhances user experience by providing actionable information.

However, I notice that the original error message mentioned "slack or github" options, but the new message only mentions Slack. If GitHub is no longer a supported option, this change is correct. If GitHub is still supported, you might want to update the error message to include how to configure GitHub as well.


🏁 Script executed:

#!/bin/bash
# Check if there are any references to GitHub as a drift mode elsewhere in the codebase
echo "Checking for GitHub as a drift notification option in the code..."
rg -i "github.*drift" --type go

Length of output: 5358


Action: Update drift mode error message to include GitHub configuration details.

  • The error message in cli/pkg/drift/Provider.go (line 22) currently only instructs users to specify Slack notifications via the environment variable INPUT_DRIFT_DETECTION_SLACK_NOTIFICATION_URL.
  • Verification confirms that GitHub drift notifications are still referenced and appear to be supported (e.g., through usages of INPUT_DRIFT_GITHUB_ISSUES and references in files like cli/pkg/github/github.go and ee/cli/pkg/drift/provider.go).
  • Please update the error message to either include guidance on configuring GitHub notifications (for example, by mentioning INPUT_DRIFT_GITHUB_ISSUES) or clarify that drift mode now supports only Slack, if that change is intentional.

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