ci: fix jampack

[maehr]

Pull request

Going from

to

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.

Summary by CodeRabbit

Summary by CodeRabbit

• New Features

  • Enhanced GitHub Actions workflow for improved rendering and publishing of Quarto projects.
  • Introduced a dedicated step for rendering the project to streamline HTML output generation.

• Improvements

  • Updated the pull request template to require contributors to mention co-authors, enhancing documentation and co-authorship recognition.
  • Optimized the publishing job to specify the content directory and prevent unnecessary rendering during the publish step, enhancing workflow efficiency.

[coderabbitai]

Walkthrough

The changes enhance the GitHub Actions workflow for a Quarto project by introducing a dedicated rendering step that generates HTML output from the manuscript directory. Additionally, a new checklist in the pull request template requires contributors to acknowledge co-authors, promoting better attribution. These updates improve the clarity and efficiency of both the development process and the workflow.

Changes

File	Change Summary
.github/pull_request_template.md	Added requirement for co-authors to be mentioned in PR description using Co-authored-by: format.
.github/workflows/quarto-publish.yml	Added "Render Quarto Project" step for HTML output; specified path: _site for publishing; set render: false to avoid redundant rendering.

Poem

🐰 In the meadow where the workflows play,
A new step hops in, brightening the day.
HTML shines from the manuscript's heart,
With each little change, we're crafting our art.
Publishing now dances in clear, joyful rhyme,
As rendering hops along, keeping perfect time! 🌼✨

---

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4adf811 and 079f912.

Files selected for processing (1)

• .github/workflows/quarto-publish.yml (2 hunks)

Additional comments not posted (2)

.github/workflows/quarto-publish.yml (2)

53-57: LGTM! The rendering step is well-configured.

The addition of the "Render Quarto Project" step using quarto-dev/quarto-actions/render@v2 is correctly set up to render the project in the manuscript directory to HTML. This enhances clarity by separating rendering from publishing.

---

84-85: LGTM! The publish step is optimized.

The "Publish to GitHub Pages" step correctly specifies the _site directory for published content and sets render to false to avoid redundant rendering, optimizing the workflow.

[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 079f912 and 72bbebe.

Files selected for processing (2)

• .github/pull_request_template.md (1 hunks)
• .github/workflows/quarto-publish.yml (2 hunks)

Files skipped from review due to trivial changes (1)

• .github/pull_request_template.md

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/quarto-publish.yml