Fixes #3320 added styles from OrgUpdate.module.css to app.module.css

[NischalPaliwal]

What kind of change does this PR introduce?
refactoring

Issue Number:
#3320
Fixes #3320

Snapshots/Videos:

If relevant, did you update the documentation?
No

Summary

1. Added the styles from OrgUpdate.module.css to app.module.css
2. Updated the imports
3. Deleted the OrgUpdate.module.css file.

Does this PR introduce a breaking change?
No

Checklist

CodeRabbit AI Review

• I have reviewed and addressed all critical issues flagged by CodeRabbit AI
• I have implemented or provided justification for each non-critical suggestion
• I have documented my reasoning in the PR comments where CodeRabbit AI suggestions were not implemented

Test Coverage

• I have written tests for all new changes/features
• I have verified that test coverage meets or exceeds 95%
• I have run the test suite locally and all tests pass

Other information

Have you read the contributing guide?
Yes

Summary by CodeRabbit

• Style
  • Moved styling for organization update component from a local module to a global style file
  • Preserved existing styles for message and icon classes

[coderabbitai]

Walkthrough

This pull request focuses on refactoring CSS files for the OrgUpdate component by moving styles from a local module CSS file to the global app.module.css. The changes involve removing the local OrgUpdate.module.css file and updating the import statement in the corresponding TypeScript component to use the global CSS file. This is part of a broader effort to streamline CSS management and improve the application's UI/UX.

Changes

File	Change Summary
src/components/OrgSettings/General/OrgUpdate/OrgUpdate.module.css	Deleted CSS file with .message and .icon classes
src/components/OrgSettings/General/OrgUpdate/OrgUpdate.tsx	Updated import statement to use ../../../../style/app.module.css
src/style/app.module.css	Added .message and .icon classes from the deleted local CSS file

Assessment against linked issues

Objective	Addressed	Explanation
Streamline CSS into a single global file [#3320]	✅
Delete local CSS files after merging [#3320]	✅
Reference only global CSS file [#3320]	✅
Use descriptive variable names for colors [#3320]	❓	Need to verify color variable naming

Possibly related issues

• Refactor CSS files in src/screens/OrgSettings #2523: Refactoring CSS files in src/screens/OrgSettings, which follows a similar pattern of consolidating CSS
• Refactor CSS files in src/screens/OrgList #2521: Refactoring CSS files in src/screens/OrgList, part of the broader CSS streamlining effort
• Refactor CSS files in src/screens/OrgContribution #2520: Refactoring CSS files in src/screens/OrgContribution, consistent with the current PR's approach

Possibly related PRs

• Refactor styles: move SubTags.module.css styles to app.module.css #2538: Moving styles from SubTags.module.css to app.module.css
• refactored OrganizationDashboard css/ closes #2513 #2593: Refactoring OrganizationDashboard.module.css styles
• Refactor CSS for LeftDrawerOrg #3131: Moving styles from LeftDrawerOrg.module.css to app.module.css

Suggested reviewers

• palisadoes

Poem

🐰 CSS files hopping away,
Styles now global, hip hooray!
One file to rule them all, so neat,
Our code's now looking quite a treat!
Refactoring rabbit's delight! 🎨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d02edfa and 07051ce.

📒 Files selected for processing (3)

• src/components/OrgSettings/General/OrgUpdate/OrgUpdate.module.css (0 hunks)
• src/components/OrgSettings/General/OrgUpdate/OrgUpdate.tsx (1 hunks)
• src/style/app.module.css (1 hunks)

💤 Files with no reviewable changes (1)

• src/components/OrgSettings/General/OrgUpdate/OrgUpdate.module.css

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

• src/components/OrgSettings/General/OrgUpdate/OrgUpdate.tsx

🔇 Additional comments (2)

src/style/app.module.css (2)

8948-8954: LGTM! Clean flexbox implementation for message container.

The .message class correctly implements flexbox for centering content both vertically and horizontally with proper flex direction.

---

8956-8960: LGTM! Well-structured icon styling.

The .icon class follows CSS best practices with proper use of transform and color variables.

---

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

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

1. We don't merge PRs with poor code quality.
   1. Follow coding best practices such that CodeRabbit.ai approves your PR.
2. We don't merge PRs with failed tests.
   1. When tests fail, click on the Details link to learn more.
   2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
   3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make