i.visible = !i.visible"
v-if="i.visible"
>
```
--------------------------------
### Rebase and force push updates
Source: https://github.com/le5le-com/meta2d.js/blob/main/CONTRIBUTING.md
If changes are suggested for your Pull Request, rebase your branch to incorporate them and then force push to update your Pull Request. This ensures the PR reflects the latest changes.
```shell
git rebase master -i
git push -f
```
--------------------------------
### Commit changes
Source: https://github.com/le5le-com/meta2d.js/blob/main/CONTRIBUTING.md
Commit your changes using a descriptive message that follows the project's conventions. The `-a` flag can be used to automatically stage and commit modified files.
```shell
git commit -a
```
--------------------------------
### Push branch to GitHub
Source: https://github.com/le5le-com/meta2d.js/blob/main/CONTRIBUTING.md
After committing your changes, push your feature branch to your GitHub repository to prepare for a pull request.
```shell
git push origin my-fix-branch
```
--------------------------------
### Checkout Master Branch
Source: https://github.com/le5le-com/meta2d.js/blob/main/CONTRIBUTING.md
Command to switch to the local master branch, forcing the checkout if necessary.
```shell
git checkout master -f
```
--------------------------------
### Create a new git branch
Source: https://github.com/le5le-com/meta2d.js/blob/main/CONTRIBUTING.md
Before submitting a Pull Request, create a new git branch for your changes. This helps in organizing contributions.
```shell
git checkout -b my-fix-branch master
```
--------------------------------
### Commit Message Header Format
Source: https://github.com/le5le-com/meta2d.js/blob/main/CONTRIBUTING.md
The standard format for the header of a git commit message, including type, optional scope, and subject.
```git