Skip to content

corrected the organisation to organization #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Preeti9764
Copy link
Contributor

@Preeti9764 Preeti9764 commented Jun 23, 2025

📌 Fixes

Fixes #155


📝 Summary of Changes

changed organisation -> organization .

📸 Screenshots / Demo (if UI-related)

image


Summary by Sourcery

Standardize spelling of "organization" across the extension

Enhancements:

  • Standardize spelling of "organization" in UI labels, tooltips, and placeholders
  • Update console logs, toast messages, and error throws to use "organization"

Copy link
Contributor

sourcery-ai bot commented Jun 23, 2025

Reviewer's Guide

This PR standardizes the spelling of “organization” across the UI and scripts, replacing all instances of “organisation” with “organization” in headings, tooltips, placeholders, console logs, toast notifications, and error messages.

File-Level Changes

Change Details Files
Normalized spelling in UI copy
  • Updated heading text from “Organisation” to “Organization”
  • Adjusted tooltip title, description, and labels
  • Replaced input placeholder text
src/popup.html
Normalized spelling in script messages
  • Updated console log messages to use “Organization”
  • Revised toast notification text for invalid or missing org
  • Corrected thrown error messages in scrumHelper
src/scripts/popup.js
src/scripts/scrumHelper.js

Assessment against linked issues

Issue Objective Addressed Explanation
#155 Standardize the spelling of 'organisation' to 'organization' throughout the codebase.

Possibly linked issues


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. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard 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

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @Preeti9764 - I've reviewed your changes - here's some feedback:

  • Perform a project-wide search/replace to catch any residual instances of the British spelling in code, logs, or tests.
  • Review the updated UI copy for typos and case consistency—e.g. change “activites” to “activities” and fix the uppercase “Z” in “Which organiZation’s” to plain “organization.”
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Perform a project-wide search/replace to catch any residual instances of the British spelling in code, logs, or tests.
- Review the updated UI copy for typos and case consistency—e.g. change “activites” to “activities” and fix the uppercase “Z” in “Which organiZation’s” to plain “organization.”

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@Preeti9764 Preeti9764 changed the title correct the organization corrected the organisation to organization Jun 23, 2025
@Preeti9764 Preeti9764 self-assigned this Jun 23, 2025
@Preeti9764 Preeti9764 requested review from vedansh-5 and hpdang June 23, 2025 18:10
Copy link
Contributor

@vedansh-5 vedansh-5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm! Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Organisation --> organization
2 participants