fix: attempt to shift upload to build

[cmeesters]

yet another attempt to enable slide (artifact) upload along source material

Summary by CodeRabbit

• New Features
  • Introduced a new step in the release workflow to upload PDF slides as artifacts when a release is created.
• Improvements
  • Enhanced control flow for the upload process, ensuring it only occurs under specific conditions related to release creation.

[coderabbitai]

Walkthrough

The pull request introduces a new step in the GitHub Actions workflow file .github/workflows/release-please.yml, specifically adding an "Upload Release Artifacts" step. This step is conditioned to execute only if a release has been created. It uses the actions/upload-artifact@v4 action to upload PDF files from the slides directory, naming the artifact "Slides." This restructuring clarifies the control flow for uploading release artifacts based on the release creation status.

Changes

Files	Change Summary
.github/workflows/release-please.yml	Added a step to upload release artifacts, conditioned on release creation, using upload-artifact.

Possibly related PRs

• fix: attempt to upload artifacts #130: This PR also modifies the .github/workflows/release-please.yml file to enhance the upload process of release artifacts, indicating a direct connection in the workflow management related to artifact uploads.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 915b3d4 and 07273a1.

Files selected for processing (1)

• .github/workflows/release-please.yml (2 hunks)

Additional context used

actionlint

.github/workflows/release-please.yml

38-38: property "release" is not defined in object type {}

(expression)

Additional comments not posted (1)

.github/workflows/release-please.yml (1)

37-43: LGTM!

The changes are approved for the following reasons:

• The new step aligns with the PR objectives of uploading slides (artifacts) alongside the source material.
• The condition to execute the step only if a release has been created is a good practice to ensure that artifacts are uploaded only when necessary.
• The step is correctly implemented using the actions/upload-artifact@v4 action to upload PDF files from the slides directory.

Tools

actionlint

38-38: property "release" is not defined in object type {}

(expression)

---

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

[github-actions]

Artifacts

• Slides