add otelcol-sampling workflows

[jpkrohling]

Signed-off-by: Juraci Paixão Kröhling juraci@kroehling.de

[coderabbitai]

Walkthrough

The recent updates introduce two new GitHub Actions workflows specifically for the otelcol-sampling project. One workflow (ci-otelcol-sampling.yaml) is designed to handle continuous integration tasks using GoReleaser, while the other (release-otelcol-sampling.yaml) is aimed at managing the release process for otelcol-sampling distributions when new releases are published.

Changes

File Path	Change Summary
.github/workflows/ci-otelcol-sampling.yaml	Introduces a CI workflow for otelcol-sampling using GoReleaser.
.github/workflows/release-otelcol-sampling.yaml	Sets up a workflow for releasing otelcol-sampling distributions on published releases.

Poem

In the land of code, where workflows rise,
New paths are paved beneath the skies.
For otelcol-sampling, CI's now in flight,
And releases shine, oh what a sight!
With GoReleaser, our tasks align,
Hopping forward, projects refine. 🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

[coderabbitai]

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 e2fdfc3 and 08d547b.

Files selected for processing (2)

• .github/workflows/ci-otelcol-sampling.yaml (1 hunks)
• .github/workflows/release-otelcol-sampling.yaml (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/release-otelcol-sampling.yaml

Additional comments not posted (1)

.github/workflows/ci-otelcol-sampling.yaml (1)

1-15: Workflow setup looks good for CI using GoReleaser.

Verification successful

---

The base GoReleaser CI workflow file is correctly configured and includes the necessary steps for setting up the environment and running GoReleaser for the specified distribution.

• The workflow accepts a distribution input, which is required and of type string.
• It includes steps for checking out the repository, setting up QEMU, Docker Buildx, and Go, downloading SBOM, generating sources, and running GoReleaser with the specified distribution.

This confirms that the ci-otelcol-sampling.yaml workflow is correctly set up to use the base GoReleaser CI workflow.

Scripts executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify the existence and basic configuration of the base GoReleaser CI workflow.

# Test: Check if the base workflow file exists.
if [ -f .github/workflows/base-goreleaser-ci.yaml ]; then
  echo "Base GoReleaser CI workflow file exists."
else
  echo "Base GoReleaser CI workflow file does not exist."
fi

Length of output: 145

---

---

Script:

#!/bin/bash
# Description: Check the contents of the base GoReleaser CI workflow file for relevant configurations.

# Display the contents of the base workflow file.
cat .github/workflows/base-goreleaser-ci.yaml

Length of output: 1097