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: fix ci #55

Merged
merged 10 commits into from
Aug 29, 2024
Merged

ci: fix ci #55

merged 10 commits into from
Aug 29, 2024

Conversation

maehr
Copy link
Contributor

@maehr maehr commented Aug 29, 2024

Pull request

Proposed changes

Types of changes

  • New feature (non-breaking change which adds functionality).
  • Enhancement (non-breaking change which enhances functionality)
  • Bug Fix (non-breaking change which fixes an issue).
  • Breaking change (fix or feature that would cause existing functionality to change).

Checklist

  • I have read the README document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have mentioned all co-authors in the PR description as Co-authored-by: Name <[email protected]>.

Summary by CodeRabbit

  • Chores
    • Updated the GitHub Actions workflow to specify a more stable operating system environment for builds, enhancing compatibility and reliability.
    • Upgraded the Quarto Actions version in the workflow, potentially improving performance and compatibility with new features.
    • Adjusted the operating system environment for lint and build-deploy jobs to macOS, which may influence job behavior and dependency compatibility.

Copy link
Contributor

coderabbitai bot commented Aug 29, 2024

Walkthrough

The change involves updating the GitHub Actions workflow configuration by modifying the operating system environment for multiple jobs and upgrading the version of the Quarto Actions used. The runs-on attribute has been changed from ubuntu-latest to macos-latest for the lint and build-deploy jobs, and the uses attribute for the Render Quarto Project step has been updated from quarto-dev/quarto-actions/render@v2 to quarto-dev/quarto-actions/[email protected]. These adjustments may influence compatibility and performance during the workflow execution.

Changes

Files Change Summary
.github/workflows/quarto-publish.yml Changed runs-on from ubuntu-latest to macos-latest for lint and build-deploy; updated uses from quarto-dev/quarto-actions/render@v2 to quarto-dev/quarto-actions/[email protected]

Poem

🐇 In the meadow where the bunnies play,
A change was made, hip-hip-hooray!
From Ubuntu to macOS, we leap with glee,
For smoother hops and scripts that flow free.
With every build, we'll dance and cheer,
A joyful leap, the future's near! 🌼


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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 29e792e and 29f3f62.

Files selected for processing (1)
  • .github/workflows/quarto-publish.yml (1 hunks)
Additional comments not posted (1)
.github/workflows/quarto-publish.yml (1)

38-38: LGTM! But verify compatibility with ubuntu-20.04.

The change from ubuntu-latest to ubuntu-20.04 is approved. However, ensure that all dependencies and scripts are compatible with ubuntu-20.04.

The code changes are approved.

Run the following script to verify the compatibility of dependencies and scripts with ubuntu-20.04:

Verification successful

Change to ubuntu-20.04 is compatible with the workflow.

The actions and scripts used in the workflow are standard and should work without issues on ubuntu-20.04. No compatibility problems were found with the current setup.

  • Node.js and Python setup actions are compatible.
  • npm and pip commands are standard and supported.
  • quarto-dev actions should work as expected.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of dependencies and scripts with `ubuntu-20.04`.

# Test: Check for any compatibility issues in the workflow file. Expect: No issues.
grep -r 'ubuntu-20.04' .github/workflows/

Length of output: 104


Script:

#!/bin/bash
# Description: Check for package installations and scripts in the workflow file to assess compatibility with `ubuntu-20.04`.

# Search for package installations and script executions in the workflow file.
grep -E 'run:|uses:' .github/workflows/quarto-publish.yml -A 2

Length of output: 1646

@maehr maehr changed the title ci: downgrade ubuntu runner ci: fix ci Aug 29, 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 29f3f62 and 9774485.

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

@maehr
Copy link
Contributor Author

maehr commented Aug 29, 2024

@mtwente I am out of ideas for the moment. The debugging is harder than thought...

@maehr maehr requested a review from mtwente August 29, 2024 15:44
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 9774485 and 73194d8.

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

20-20: LGTM! But verify compatibility with macOS.

The change to macos-latest for the lint job looks good. However, ensure that all dependencies and tools used in this job are compatible with macOS.

Run the following script to verify the compatibility:

Verification successful

No macOS-specific compatibility issues found for the lint job.

The change to macos-latest for the lint job does not introduce any macOS-specific dependencies or tools that could cause compatibility issues. Ensure that the Node.js version requirement (>=v18) is satisfied in the macOS environment.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the compatibility of the `lint` job with macOS.

# Test: Check for any macOS-specific dependencies or tools.
rg --type yaml -A 5 $'lint'

Length of output: 3352


38-38: LGTM! But verify compatibility with macOS.

The change to macos-latest for the build-deploy job looks good. However, ensure that all dependencies and tools used in this job are compatible with macOS.

Run the following script to verify the compatibility:

@maehr
Copy link
Contributor Author

maehr commented Aug 29, 2024

@mtwente I have no clue why macos works, but it does. I had to use this workaround for the metadata manual as well...

Ps: perhaps the gh action needs some fine tuning to check for chromium in a better way https://github.com/quarto-dev/quarto-actions/blob/main/render/action.yml

@mtwente mtwente merged commit 6b48645 into digihistch24:main Aug 29, 2024
3 checks passed
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.

2 participants