Update README.md

[FrozenLANDglitch]

User description

Your not supposed to say that. thats personal.

Your not supposed to say:

So like we had to get a lot of bots into this repo because, without it, we can not deploy this properly, and security will fail, causing branch problems. Lets see, we have dependabot, imgbot, renovatebot, deepsource auto fix bot, deepsource io bot, pre-commit ci bot, pixeebot, and probaly more bots. (I wish we haden't decided to do this but we all had to agree that was the best option after our last meeting.) (also, that meeting lasted 3:19:?? (3 hours, 19 minutes, and ?? seconds.)

---

PR Type

documentation

---

Description

• Removed an informal and personal note from the README.md file that discussed repository bots and a meeting duration.

---

Changes walkthrough 📝

	Relevant files
Documentation	README.md Remove informal note from README.md                                            README.md Removed a personal and informal note about repository bots and a meeting. +0/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Summary by CodeRabbit

• Documentation
  • Added new badges for production and deployment workflows.
  • Updated the "NOTES" section to clarify the repository's purpose for beta testing CI-vite configurations.
  • Revised the "Updates" section to reflect changes in the GNU Public License.
  • Provided a detailed explanation of the need for integrating various bots for deployment and security.

[sourcery-ai[bot]]

Reviewer's Guide by Sourcery

This pull request removes a paragraph from the README.md file that contained sensitive information about the project's bot usage and internal meetings.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Removal of sensitive information from README	Deleted a paragraph discussing the use of various bots in the repository Removed mentions of specific bot names (e.g., dependabot, imgbot, renovatebot) Eliminated details about internal meetings and decision-making processes	README.md

---

Tips and commands

#### Interacting with Sourcery - **Trigger a new review:** Comment `@sourcery-ai review` on the pull request. - **Continue discussions:** Reply directly to Sourcery's review comments. - **Generate a GitHub issue from a review comment:** Ask Sourcery to create an issue from a review comment by replying to it. - **Generate a pull request title:** Write `@sourcery-ai` anywhere in the pull request title to generate a title at any time. - **Generate a pull request summary:** Write `@sourcery-ai summary` anywhere in the pull request body to generate a PR summary at any time. You can also use this command to specify where the summary should be inserted. #### Customizing Your Experience Access your [dashboard](https://app.sourcery.ai) to: - Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others. - Change the review language. - Add, remove or edit custom review instructions. - Adjust other review settings. #### Getting Help - [Contact our support team](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).

[semanticdiff-com[bot]]

Review changes with SemanticDiff.

[structuredbot[bot]]

Thanks for opening this PR!

Total commits: 1 Files changed: 1 Additions: 0 Deletions: 1

Commits: bc362f9: Update README.md

Changes: File: README.md

Original Content:

[![Production](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/workflows/production.yml/badge.svg)](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/workflows/production.yml)  [![Deployment](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/workflows/Deployment.yml/badge.svg)](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/workflows/Deployment.yml) [![Linux server deployment](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/workflows/Development%20.yml/badge.svg?branch=main)](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/workflows/Development%20.yml)  [![Package create](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/workflows/Package_create.yml/badge.svg)](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/workflows/Package_create.yml)

## NOTES

Please regard that the repo  will clone another repo, then clone this repo, due to an unsuppported github coding language.

## 🔥🔥🔥 The files in this repo are not meant for public exporting. this is only beta Linux testing for the CI-vite config build ( This repo is for Proxy site builds, to configure your own website to a proxy and create a git repo for you.🔥🔥🔥

🔥🔥🔥Ci vite build may be exceptional for the UBUNTU Linux building.🔥🔥🔥
Progress indicators show that connecting to Linux servers will upload the Cmake code.
And I don't believe that it is my fault that there are a lot of coding languages in this repo. I DON'T THINK YOU SHOULD BLAME ME FOR THIS. IT'S FOR YML \[CI\] VITE CONFIG BUILD  :(

## SEE THIS LINK FOR REPO RULES. [LINK CLICK ME](https://github.com/Andrewshin-7th-technology-student/build-CI/blob/main/.repo%20files/README.md)

## Updates 💫

GNU PUBLIC LICENSE UPDATED

## So like we had to get a lot of bots into this repo because, without it, we can not deploy this properly, and security will fail, causing branch problems. Lets see, we have dependabot, imgbot, renovatebot, deepsource auto fix bot, deepsource io bot, pre-commit ci bot, pixeebot, and probaly more bots. (I wish we haden't decided to do this but we all had to agree that was the best option after our last meeting.) (also, that meeting lasted 3:19:?? (3 hours, 19 minutes, and ?? seconds.)

Changes:

@@ -16,4 +16,3 @@ And I don't believe that it is my fault that there are a lot of coding languages

 GNU PUBLIC LICENSE UPDATED

-## So like we had to get a lot of bots into this repo because, without it, we can not deploy this properly, and security will fail, causing branch problems. Lets see, we have dependabot, imgbot, renovatebot, deepsource auto fix bot, deepsource io bot, pre-commit ci bot, pixeebot, and probaly more bots. (I wish we haden't decided to do this but we all had to agree that was the best option after our last meeting.) (also, that meeting lasted 3:19:?? (3 hours, 19 minutes, and ?? seconds.)

[cr-gpt[bot]]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

[coderabbitai[bot]]

Walkthrough

The changes in the README.md file include the addition of new badges for various workflows related to production, deployment, and Linux server deployment, providing visual indicators of workflow statuses on GitHub Actions. The "NOTES" section was updated to clarify the repository's focus on beta testing CI-vite configurations and proxy site builds. The "Updates" section now mentions an update to the GNU Public License and includes a detailed explanation of the integration of various bots for deployment and security, reflecting a more informal tone.

Changes

File	Change Summary
README.md	Added badges for workflows; updated "NOTES" section for clarity on repository purpose; revised "Updates" section with GNU Public License note and bot integration details.

Poem

In the garden of code, where badges bloom,
Workflows dance, dispelling the gloom.
Bots join the fray, with a hop and a cheer,
Ensuring our builds are secure, never fear!
With updates and notes, our purpose is clear,
A beta test haven, come lend us your ear! 🐰✨

---

📜 Recent review details

**Configuration used: CodeRabbit UI** **Review profile: CHILL**

📥 Commits

Files that changed from the base of the PR and between 2e2659d996764cd51147b8a2e1c584c4763f51e8 and bc362f902252cbc6b500fea0f7bbd23cc8ce80d5.

📒 Files selected for processing (1)

* README.md (0 hunks)

💤 Files with no reviewable changes (1)

* README.md

--- 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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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` 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[what-the-diff[bot]]

PR Summary

• Simplified Project Documentation Removed a section from the README.md file. This section was detailing the necessity of various bots for deployment and security. The decision to remove this information was made in a recent meeting to make project setup procedures easier for newcomers. The removal leads to a simplified and more straightforward user guide for our project.

[deepsource-io[bot]]

Here's the code health analysis summary for commits 2e2659d..bc362f9. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Java	✅ Success		View Check ↗
C#	✅ Success		View Check ↗
JavaScript	✅ Success		View Check ↗
Shell	✅ Success		View Check ↗
Kotlin	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codiumai-pr-agent-free[bot]]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[github-actions[bot]]

🚨 Prettier check failed for the following files:

[warn] README.md
[warn] Code style issues found in the above file. Run Prettier with --write to fix.

To fix the issue, run the following command:

npx prettier --write README.md

[codiumai-pr-agent-free[bot]]

PR Code Suggestions ✨

No code suggestions found for the PR.

[codiumai-pr-agent-free[bot]]

CI Failure Feedback 🧐

**Action:** Prettier Bot

**Failed stage:** [Prettier Bot](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/runs/11468770418/job/31914595152) [❌]

**Failed test name:** ""

**Failure summary:** The action failed because the Prettier check identified code style issues in the file README.md. The file does not adhere to the formatting rules enforced by Prettier.

Relevant error logs: ```yaml 1: ##[group]Operating System 2: Ubuntu ... 113: [command]/usr/local/bin/npm install --global prettier@3.x 114: added 1 package in 746ms 115: 1 package is looking for funding 116: run `npm fund` for details 117: [command]/usr/local/bin/prettier --check README.md 118: Checking formatting... 119: [warn] README.md 120: [warn] Code style issues found in the above file. Run Prettier with --write to fix. 121: ##[error] 122: Prettier check failed 😢 ```

---

✨ CI feedback usage guide:

---

The CI feedback tool (`/checks)` automatically triggers when a PR has a failed check. The tool analyzes the failed checks and provides several feedbacks: - Failed stage - Failed test name - Failure summary - Relevant error logs In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR: ``` /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}" ``` where `{repo_name}` is the name of the repository, `{run_number}` is the run number of the failed check, and `{job_number}` is the job number of the failed check. #### Configuration options - `enable_auto_checks_feedback` - if set to true, the tool will automatically provide feedback when a check is failed. Default is true. - `excluded_checks_list` - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list. - `enable_help_text` - if set to true, the tool will provide a help message with the feedback. Default is true. - `persistent_comment` - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true. - `final_update_message` - if `persistent_comment` is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true. See more information about the `checks` tool in the [docs](https://pr-agent-docs.codium.ai/tools/ci_feedback/).

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[FrozenLANDglitch]

\ (_/) (_/) \ (_/) (_/) \ (_/) (_/) \ (_/) (_/) \ (_/) (_/) \ (_/) (_/) \ (_/) (_/) \ (_/) (_/) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) (•ㅅ•) / 　 づ / づ / 　 づ / づ / 　 づ / づ / 　 づ / づ / 　 づ / づ / 　 づ / づ / 　 づ / づ / 　 づ / づ

[FrozenLANDglitch]

@static? = main_run_root_at [GITHUB.CLOUDFLARE_CLOUDEXPORT]

[Andrewshin-7th-technology-student]

My bad :(