Integrated code lifecycle: Improve consistency of titles in build overview

[MaximilianAnzinger]

Checklist

General

• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

Description

Fix titles of build job queue to be title case.

Steps for Testing

Prerequisites:

• 1 Instructor
• 1 Course

1. Log in to Artemis
2. Navigate to Course Administration > Build Overview
3. Check that the titles of the three tables are in title case (german & english translation)

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.

Review Progress

Code Review

• no code, just translation :)

Manual Tests

• Test 1
• Test 2

Summary by CodeRabbit

• Bug Fixes
  • Updated capitalization for localization strings to ensure consistency in the user interface.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the buildAgents.json localization file. Specifically, the casing of certain string values has been modified to ensure consistent capitalization. The strings "Running build jobs" and "Recent build jobs" have been changed to "Running Build Jobs" and "Recent Build Jobs," respectively.

Changes

File Path	Change Summary
src/main/webapp/i18n/en/buildAgents.json	Updated casing for "runningBuildJobs" and "recentBuildJobs" strings.

Possibly related PRs

• Integrated code lifecycle: Separate build agent summary and details view #8395: Modifies buildAgents.json by adding new keys related to build agents.
• Integrated code lifecycle: Change build queue page to build overview #8896: Updates the buildQueue.json file, focusing on consistent terminology across localization files.
• Development: Fix diverging translations #9471: Addresses inconsistencies in translation keys across various localization files, including buildAgents.json.

Suggested labels

documentation, ready for review

Suggested reviewers

• BBesrour
• SimonEntholzer
• krusche
• EneaGore

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 1786886 and 639225c.

📒 Files selected for processing (1)

• src/main/webapp/i18n/en/buildAgents.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/main/webapp/i18n/en/buildAgents.json

---

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

[HawKhiem]

Tested on TS3. Works as expected

[github-actions]

⚠️ Unable to deploy to test servers ⚠️

Testserver "artemis-test1.artemis.cit.tum.de" is already in use by PR #9785.

[alekspetrov9e]

Tested on TS3. Works accordingly.

[Cathy0123456789]

Tested on TS3. Looks good

[github-actions]

⚠️ Unable to deploy to test servers ⚠️

Testserver "artemis-test3.artemis.cit.tum.de" is already in use by PR #9744.