ci: fix deployment in sveltekitci.yml

[maehr]

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.

Summary by CodeRabbit

• Chores
  • Updated CI workflow conditions for caching, build actions, and deployment specific to the repository "Stadt-Geschichte-Basel/stadtgeschichtebasel.ch".

[changeset-bot]

⚠️ No Changeset found

Latest commit: 584c904

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The recent modifications to the workflow configuration involve adding conditions that tailor the CI process for the repository "Stadt-Geschichte-Basel/stadtgeschichtebasel.ch". These changes ensure that certain steps like caching, artifact uploading, and deployment are executed specifically when the workflow is run in the context of this repository, providing a more customized and efficient CI pipeline.

Changes

File	Summary
.github/workflows/.../sveltekitci.yml	Updated to include conditional checks for the repository "Stadt-Geschichte-Basel/stadtgeschichtebasel.ch" for steps like caching, post-build actions, artifact upload, and deployment.

Poem

🐇✨
In the land of code, where the SvelteKit lies,
A CI pipeline under Basel skies.
Checks and builds, with conditions so wise,
Tailored flows that the rabbit implies. 🚀🌟

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 7cd893e and 584c904.

Files selected for processing (1)

• .github/workflows/sveltekitci.yml (3 hunks)

Additional comments: 4

.github/workflows/sveltekitci.yml (4)

• 47-47: The conditional check added to the 'Setup jampack cache' step is correct and consistent with the PR objectives.
• 59-59: The conditional check added to the 'Postbuild' step is correct and consistent with the PR objectives.
• 64-69: The conditional check added to the 'Upload build artifact' step is correct and consistent with the PR objectives. However, ensure that the retention-days set to 1 is intentional and aligns with the project's artifact retention policy.
• 71-71: The conditional check added to the 'deploy' job is correct and consistent with the PR objectives.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	584c904
Status:	✅  Deploy successful!
Preview URL:	https://090164f7.stadtgeschichtebasel-ch.pages.dev
Branch Preview URL:	https://ci-fix-deployment.stadtgeschichtebasel-ch.pages.dev

View logs