Development: Add staging deployment

[gbanu]

This PR is used to test the staging deployments

Summary by CodeRabbit

• New Features
  • The homepage title has been updated to "Staging deployment Helios." This change refreshes the welcome message displayed on the main landing page, ensuring that users see the most current and relevant information when they visit the site.

[coderabbitai]

Walkthrough

This pull request updates the English internationalization file for the home page by modifying the title value. The original title "Welcome to Artemis!" has been replaced with "Staging deployment Helios", with no other changes made to the file’s structure or content.

Changes

File	Change Summary
src/.../i18n/en/home.json	Changed the title key value from "Welcome to Artemis!" to "Staging deployment Helios"

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 generate docstrings to generate docstrings for this PR. (Beta)
• @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 or @coderabbitai title anywhere in the PR title to generate the title automatically.

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

🧹 Nitpick comments (1)

src/main/webapp/i18n/en/home.json (1)

3-3: Consider a more maintainable approach for environment-specific configurations.

Instead of hardcoding the environment name in the i18n file, consider:

1. Using environment variables or configuration files to set environment-specific values
2. Adding a visual indicator (e.g., banner/badge) for non-production environments that reads from the deployment configuration

This would make it easier to manage different environments without modifying the i18n files.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3c8453c and 7a64211.

⛔ Files ignored due to path filters (2)

• .github/workflows/staging-deployment.yml is excluded by !**/*.yml
• .github/workflows/testserver-deployment.yml is excluded by !**/*.yml

📒 Files selected for processing (1)

• src/main/webapp/i18n/en/home.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: Call Build Workflow / Build .war artifact
• GitHub Check: Call Build Workflow / Build and Push Docker Image
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: server-style
• GitHub Check: client-tests
• GitHub Check: client-style
• GitHub Check: server-tests
• GitHub Check: Analyse

🔇 Additional comments (1)

src/main/webapp/i18n/en/home.json (1)

3-3: LGTM - Clear staging environment indicator.

The title change helps users clearly identify that they are on the staging environment, which is important for testing purposes.