fix: fix image artifact regex to match GitHub Actions filename

[aliciaaevans]

GitHub Actions doesn't allow artifact files to contain :, so it is replaced with ---. Update this artifact finding code to match that pattern.

[coderabbitai]

Walkthrough

The pull request introduces a modification to the regular expression used for matching image names in the bioconda_utils/artifacts.py file. Specifically, the regular expression pattern IMAGE_RE has been updated from r"(.+)(?::|%3A)(.+)\.tar\.gz$" to r"(.+)(?::|%3A|---)(.+)\.tar\.gz$". This change allows for an additional delimiter, ---, in the parsing of image names.

Aside from this update to the regular expression, there are no other changes to the logic, error handling, or control flow within the file. The structure and functionality of the upload_pr_artifacts function and its related helper functions remain unchanged. Additionally, there are no modifications to the parameters, return types, or the handling of artifacts from various sources, including Azure, CircleCI, and GitHub Actions. The error handling and logging mechanisms continue to function as they did previously, maintaining consistency with earlier implementations. No alterations were made to the declarations of exported or public entities in this diff.

---

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>, 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.

[coderabbitai]

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 94463a9 and e9c5b69.

📒 Files selected for processing (1)

• bioconda_utils/artifacts.py (1 hunks)

🔇 Additional comments (1)

bioconda_utils/artifacts.py (1)

21-21: Verify GitHub Actions integration end-to-end.

While the regex change is correct, please ensure:

1. The GitHub Actions workflow correctly handles the new artifact format
2. The artifact download and processing flow in get_gha_artifacts() works with the modified names

Let's check the GitHub Actions workflow files and artifact handling:

✅ Verification successful

GitHub Actions integration appears to be unaffected by the regex change

The regex change in IMAGE_RE is safe because:

1. The GitHub Actions workflow (changevisibility.yml) only uploads log files with pattern biocontainers-*.txt, not container images
2. The get_gha_artifacts() function in artifacts.py handles artifact downloads generically without relying on the modified regex pattern
3. The IMAGE_RE pattern is only used for parsing artifact names after they are downloaded, not for the GitHub Actions upload/download process itself

The integration remains intact as the artifact handling flow operates independently of the image name parsing logic.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify GitHub Actions workflow configuration and artifact handling

# Check workflow files for artifact upload configuration
echo "Checking workflow configurations:"
fd -e yml -e yaml . .github/workflows/ --exec grep -l "actions/upload-artifact"

# Look for any existing artifact handling code
echo "Checking artifact handling patterns:"
rg -l "actions/upload-artifact|actions/download-artifact" .

Length of output: 340

---

Script:

#!/bin/bash
# Let's examine the workflow file content and artifact handling code more thoroughly

# Check the content of the workflow file
echo "=== Workflow file content ==="
cat .github/workflows/changevisibility.yml

# Look for artifact-related code in the Python files
echo -e "\n=== Artifact handling code ==="
rg -A 10 "get_gha_artifacts" .

# Check for any artifact name patterns or related constants
echo -e "\n=== Artifact name patterns ==="
rg "\.tar\.gz" .

Length of output: 11453

[bgruening]

Urrgs, nice find!