fix!: Rename blocklyTreeIconOpen to blocklyToolboxCategoryIconOpen

[UtkershBasnet]

The basics

• I validated my changes

The Details

The pull request renames all references to blocklyTreeIconOpen to blocklyToolboxCategoryIconOpen

Resolves

Fixes #8348

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[github-actions]

Welcome! It looks like this is your first pull request in Blockly, so here are a couple of tips:

• You can find tips about contributing to Blockly and how to validate your changes on our developer site.
• All contributors must sign the Google Contributor License Agreement (CLA). If the google-cla bot leaves a comment on this PR, make sure you follow the instructions.
• We use conventional commits to make versioning the package easier. Make sure your commit message is in the proper format or learn how to fix it.
• If any of the other checks on this PR fail, you can click on them to learn why. It might be that your change caused a test failure, or that you need to double-check the style guide.
  Thank you for opening this PR! A member of the Blockly team will review it soon.

[BeksOmega]

Heya @UtkershBasnet in the future we ask that folks ask to be assigned to issues before completing them! Otherwise it's not fair to the other folks that may be working on it. If you do that in the future, I'll have to close your PR.

[BeksOmega]

This change looks good =) Thank you for the fix!

[UtkershBasnet]

@BeksOmega Thank you for the feedback and for reviewing my PR!

I apologize for not asking to be assigned to the issue before completing it. I understand the importance of maintaining fairness in the process and will make sure to follow this protocol in the future.

I'm glad the change looks good to you! Thank you for the review and for your guidance.

[BeksOmega]

Ah sorry, just noticed this is against the wrong branch @UtkershBasnet

To rebase onto the rc/v12.0.0 branch, you can follow these steps.

1. Fetch the latest changes from rc/v12.0.0:

   git fetch upstream rc/v12.0.0

2. Checkout your branch:

   git checkout [your-branch-name]

3. Start an interactive rebase:

   git rebase -i upstream/rc/v12.0.0

4. In the editor that opens, identify the commits that aren't yours. These are likely the ones at the top of the list.

5. Change the word pick to drop for each commit you want to remove.

6. Save and close the editor.

7. Force push your changes to your branch: Note that force pushing is a dangerous operation because it overwrites commit history, so if you dropped the wrong commits you could lose work.

   git push -f origin [your-branch-name]

Once you've done this, the PR should be on the correct branch.

Let me know if you have any questions or run into any issues!

[UtkershBasnet]

I dropped all the changes that weren't mine but still additional commits were made probably due to-

git fetch upstream rc/v12.0.0

During the rebase I wasn't given access to remove other commits which are shown now ,I could only drop 6-7 commits the last commit was mine.

[BeksOmega]

Can you try it with this slightly modified set of commands? (1 and 2 are changed)

1. Switch to the rc/v12.0.0 branch

   git switch rc/v12.0.0

2. Pull the latest changes from rc/v12.0.0:

   git pull upstream rc/v12.0.0

3. Checkout your branch:

   git switch [your-branch-name]

4. Start an interactive rebase:

   git rebase -i upstream/rc/v12.0.0

5. In the editor that opens, identify the commits that aren't yours. These are likely the ones at the top of the list.

6. Change the word pick to drop for each commit you want to remove.

7. Save and close the editor.

8. Force push your changes to your branch: Note that force pushing is a dangerous operation because it overwrites commit history, so if you dropped the wrong commits you could lose work.

   git push -f origin [your-branch-name]

[UtkershBasnet]

I think the problem was in my branch i removed the commits that weren't mine in my own branch using the

git rebase -i HEAD~n

[BeksOmega]

Thank you again for your work on this!