> To build a Wix site agentically, or add Wix features like bookings or a store to a site you already have, follow https://www.wix.com/headless/skill.md
> 
> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - If a reference page seems to be missing its schema (parameters, return types, or type definitions), append `?schema=true` to its `.md` URL (e.g. `https://dev.wix.com/docs/contexts/contexts/stores/category-info/use-category-info-context.md?schema=true`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Creating a Pull Request

## Article: Creating a Pull Request

## Article Link: https://dev.wix.com/docs/wix-design-system/contributing/creating-a-pull-request.md

## Article Content:

<!-- heading -->

# Creating a Pull Request for Wix Design System

<!-- end heading -->

<br />

> Wix Design System is available for people outside of Wix. But only internal employees are allowed to contribute _(as long as they are aligned with our design guidelines)_ and see the source code of our repository.

---

## Prerequisites

1. Code must be compatible with required React and Stylable versions mentioned in [README.md](invalid-url).
2. Your commits must be signed.

---

## Title

A pull request title should be composed as follows:

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```js
feat(ComponentName): add skin property.
  ^         ^         ^
  │         │         └── Subject
  │         └─────── Scope
  └──────────── Type
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

**Supported Types:**

- **breaking:** Indicates a visual breaking change.
- **chore**: Changes that don't modify source or test files.
- **deprecate**: Marks components, props, or features that are no longer recommended for use and will be removed in the future.
- **docs**: Changes affecting only the documentation.
- **feat**: Used for new features.
- **fix**: Used for bug fixes.
- **refactor**: Code changes that neither fix a bug nor add a feature.
- **revert**: Used when reverting a previous commit.

_NOTE: Only `breaking`, `deprecate`, `feat`, and `fix` types appear in the `changelog`._

**Supported Scope:** ComponentName.

**Supported Subject:** Short lowercase description of the PR.

---

## Sign Commits

### Motivation

For security reasons, we enforce signed commits.
This prevents attackers from using spoofed addresses.

### How to sign commits

1. [Generate](https://docs.github.com/en/github/authenticating-to-github/generating-a-new-gpg-key) a **GPG** key. Make sure you create the key with the email you use to sign in to your GitHub account, which should match the email you get when running this:

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```bash
git config --global user.email
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

If your email isn't configured, you can add it by running:

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```bash
git config --global user.email "email@example.com"
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

2. Set your [public key](https://github.com/settings/keys) on your GitHub account.
3. Use this command to commit:

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```bash
git commit -S -am "…"
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

or set automatic signing with:

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```bash
git config --global commit.gpgsign true
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

4. You can verify your commit is signed with:
<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```bash
git log --show-signature
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

Learn more about [signing commits](https://docs.github.com/en/github/authenticating-to-github/signing-commits).

_Note:_ A pull request that comes from a forked repository is **not valid** and will be treated as **unsigned** by the CI.

### FAQ

**Q: I'm not a wix employee, can I contribute to wix-design-system without signing my commits?**

**A:** No, currently we don't allow external contributions to the wix-design-system repository.

---

**Q: I'm getting the following error:**

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```bash
error: gpg failed to sign the data
fatal: failed to write commit object
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

**A:** [Tell your local git client](https://docs.github.com/en/github/authenticating-to-github/telling-git-about-your-signing-key) about your newly generated GPG key.

---

**Q: I'm getting the following error:**

<!-- grid layout -->

<!-- grid layout item -->

<!-- grid layout content -->

```bash
The user "xxx" that created this commit is not a member of the repository's organization ("wix"), PR is dangerous, will not run this build.
```

<!-- end grid layout -->

<!-- end grid layout item -->

<!-- end grid layout content -->

**A:** Make sure your pull request comes from a **cloned** repository and not a **forked** one. If you need more help, let us know.

<br>
<br>
<br>
<br>
<br>