feat: footer for beta version added

[maehr]

Pull request

• feat: footer for beta version added

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

New Features:

• Added a new footer section to the application layout. This section includes an alert message informing users that the application is currently in a testing phase, enhancing transparency and user awareness. A link for more information is also provided, improving accessibility to additional details.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b99f464

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 update introduces a new footer section to the Svelte component in the layout file. This section contains an alert message informing users that the application is currently in a testing phase, with a link provided for further information.

Changes

File	Summary
src/routes/.../+layout.svelte	A new footer fragment has been added to the Svelte component. This fragment contains an alert message about the application's testing phase and a link for more details.

Poem

🐇🍂 As the leaves fall, we code and tweak,
In the season of harvest, a new feature we sneak.
A footer alert, a message so clear,
"We're testing, we're testing, have no fear!"
A link for more info, a click away,
As we hop towards progress, day by day.
So here's to the changes, big and small,
In this wonderful season of fall. 🍂🐇

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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 help to get help.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.

Note: For conversation with the bot, please use the review comments on code diffs or files.

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

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 156dde5 and b99f464.

Files selected for processing (1)

• src/routes/+layout.svelte (1 hunks)

Files skipped from review due to trivial changes (1)

• src/routes/+layout.svelte