{

"workbench.colorCustomizations": {

"activityBar.activeBackground": "#ff333399",

"activityBar.activeBorder": "#1a1d02",

"activityBar.background": "#ff333399",

"activityBar.foreground": "#e7e7e7",

"activityBar.inactiveForeground": "#e7e7e799",

"activityBarBadge.background": "#00df00",

"activityBarBadge.foreground": "#15202b",

"sash.hoverBorder": "#ff333399",

"statusBar.background": "#ff000099",

"statusBar.foreground": "#e7e7e7",

"statusBarItem.hoverBackground": "#ff333399",

"statusBarItem.remoteBackground": "#ff000099",

"statusBarItem.remoteForeground": "#e7e7e7",

"titleBar.activeBackground": "#ff000099",

"titleBar.activeForeground": "#e7e7e7",

"titleBar.inactiveBackground": "#ff000099",

"titleBar.inactiveForeground": "#e7e7e799",

"commandCenter.border": "#e7e7e799"

},

"peacock.remoteColor": "#ff000099",

"intelephense.environment.phpVersion": "8.3.0",

"intelephense.completion.fullyQualifyGlobalConstantsAndFunctions": true,

"intelephense.phpdoc.useFullyQualifiedNames": true

}

- ci: 👷 update github issue templates & workflows

- docs: 📝 update translations & links

Full changelog: https://github.com/alexis-gss/laravel-unit-tests/compare/v1.1.1...v1.1.2

We as members, contributors, and leaders pledge to make participation in our

community a harassment-free experience for everyone, regardless of age, body

size, visible or invisible disability, ethnicity, sex characteristics, gender

identity and expression, level of experience, education, socio-economic status,

nationality, personal appearance, race, religion, or sexual identity

and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,

diverse, inclusive, and healthy community.

Examples of behavior that contributes to a positive environment for our

community include:

* Demonstrating empathy and kindness toward other people

* Being respectful of differing opinions, viewpoints, and experiences

* Giving and gracefully accepting constructive feedback

* Accepting responsibility and apologizing to those affected by our mistakes,

and learning from the experience

* Focusing on what is best not just for us as individuals, but for the

overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or

advances of any kind

* Trolling, insulting or derogatory comments, and personal or political attacks

* Public or private harassment

* Publishing others' private information, such as a physical or email

address, without their explicit permission

* Other conduct which could reasonably be considered inappropriate in a

professional setting

Community leaders are responsible for clarifying and enforcing our standards of

acceptable behavior and will take appropriate and fair corrective action in

response to any behavior that they deem inappropriate, threatening, offensive,

or harmful.

Community leaders have the right and responsibility to remove, edit, or reject

comments, commits, code, wiki edits, issues, and other contributions that are

not aligned to this Code of Conduct, and will communicate reasons for moderation

decisions when appropriate.

This Code of Conduct applies within all community spaces, and also applies when

an individual is officially representing the community in public spaces.

Examples of representing our community include using an official e-mail address,

posting via an official social media account, or acting as an appointed

representative at an online or offline event.

Instances of abusive, harassing, or otherwise unacceptable behavior may be

reported to the community leaders responsible for enforcement at

Alexis (alexis-gss).

All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the

reporter of any incident.

Community leaders will follow these Community Impact Guidelines in determining

the consequences for any action they deem in violation of this Code of Conduct:

**Community Impact**: Use of inappropriate language or other behavior deemed

unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing

clarity around the nature of the violation and an explanation of why the

behavior was inappropriate. A public apology may be requested.

**Community Impact**: A violation through a single incident or series

of actions.

**Consequence**: A warning with consequences for continued behavior. No

interaction with the people involved, including unsolicited interaction with

those enforcing the Code of Conduct, for a specified period of time. This

includes avoiding interactions in community spaces as well as external channels

like social media. Violating these terms may lead to a temporary or

permanent ban.

**Community Impact**: A serious violation of community standards, including

sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public

communication with the community for a specified period of time. No public or

private interaction with the people involved, including unsolicited interaction

with those enforcing the Code of Conduct, is allowed during this period.

Violating these terms may lead to a permanent ban.

**Community Impact**: Demonstrating a pattern of violation of community

standards, including sustained inappropriate behavior, harassment of an

individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within

the community.

This Code of Conduct is adapted from the [Contributor Covenant][homepage],

version 2.0, available at

https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct

enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at

https://www.contributor-covenant.org/faq. Translations are available at

https://www.contributor-covenant.org/translations.

Thank you for investing your time in contributing to our project !

Read our [code of conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectable.

In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.

Use the table of contents icon on the top left corner of this document to get to a specific section of this guide quickly.

To get an overview of the project, read the [readme](./README.md). Here are some resources to help you get started with open source contributions:

- [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)

- [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git)

- [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow)

- [Collaborating with pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests)

If you spot a problem with the docs, [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments).If a related issue doesn't exist, you can open a new issue using a relevant [issue form](https://github.com/alexis-gss/laravel-unit-tests/issues/new/choose).

Scan through our [existing issues](https://github.com/alexis-gss/laravel-unit-tests/issues) to find one that interests you. You can narrow down the search using `labels` as filters. See [Labels](https://github.com/alexis-gss/laravel-unit-tests/labels) for more information. If you find an issue to work on, you are welcome to open a PR with a fix.

1. Fork the repository.

- Using GitHub Desktop:

- [Getting started with GitHub Desktop](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop) will guide you through setting up Desktop.

- Once Desktop is set up, you can use it to [fork the repo](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)!

- Using the command line:

- [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them.

2. Install or update to **Node.js**, at the version specified in `.node-version`.

3. Create a working branch and start with your changes!

4. Commit the changes once you are happy with them.

When you're finished with the changes, create a pull request, also known as a PR.

- Don't forget to [link PR to issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if you are solving one.

- Enable the checkbox to [allow maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge.

Once you submit your PR, a Docs team member will review your proposal. We may ask questions or request additional information.

- We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.

- As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations).

- If you run into any merge issues, checkout this [git tutorial](https://github.com/skills/resolve-merge-conflicts) to help you resolve merge conflicts and other issues.

[](https://github.com/alexis-gss/laravel-unit-tests/blob/master/LICENSE)

- [Compatibility](#compatibility)

- [Contributing](#contributing)

- [Create a task](#create-a-task)

- [Fixing a Bug](#fixing-a-bug)

- [Proposing a Change](#proposing-a-change)

| Versions | Laravel 8^ | Laravel 9^ | Laravel 10^ | Laravel 11^ |

| :---------: | :---------: | :---------: | :---------: | :---------: |

| v1.1.2 | ✅ | ✅ | ✅ | ✅ |

| v1.1.1 | ✅ | ✅ | ✅ | ✅ |

| v1.1.0 | ✅ | ✅ | ✅ | ✅ |

| v1.0.0 | ✅ | ✅ | ✅ | ✅ |

You can create a [new issue](https://github.com/alexis-gss/laravel-unit-tests/issues/new/choose) with a specific templates : bug or feature.

Once your code is working, please run the following commands `./vendor/bin/phpstan`, `./vendor/bin/phpcs` to verify that your code is following the same coding standards (in all cases, there is github actions that check this part).

When fixing a bug please make sure to test it in several browsers. If you are not able to do so, mention that in a PR comment, so other contributors can do it.

When implementing a feature please create an issue first explaining your idea and asking whether there's need for such a feature. Remember the script's core philosophy is to stay simple and minimal, doing one thing and doing it right.

Latest version v1.1.2.

If you have encountered a potential security vulnerability in this project,

please report it to us as a [new issue](https://github.com/alexis-gss/laravel-unit-tests/issues/new/choose). We will work with you to

verify the vulnerability and patch it.

If we verify a reported security vulnerability, our policy is:

- We will patch the current release branch, as well as the immediate prior minor

release branch.

- After patching the release branches, we will immediately issue new security

fix releases for each patched release branch.

- A security advisory will be released on the project website detailing the

vulnerability, as well as recommendations for end-users to protect themselves.

"version": "1.1.2",