# Contributing

Contributions are welcome. We accept pull requests on [GitHub](https://github.com/eclipxe13/micro-catalog).

This project adheres to a
[Contributor Code of Conduct](https://github.com/eclipxe13/micro-catalog/blob/main/CODE_OF_CONDUCT.md).
By participating in this project and its community, you are expected to uphold this code.

## Team members

* [Carlos C Soto](https://github.com/eclipxe13) - original author and maintainer
* [GitHub constributors](https://github.com/eclipxe13/micro-catalog/graphs/contributors)

## Communication Channels

You can find help and discussion in the following places:

* GitHub Issues: <https://github.com/eclipxe13/micro-catalog/issues>

## Reporting Bugs

We track our bugs in our project's [issue tracker](https://github.com/eclipxe13/micro-catalog/issues).

When submitting a bug report, please include enough information for us to reproduce the bug.
A good bug report includes the following sections:

* Expected outcome
* Actual outcome
* Steps to reproduce, including sample code
* Any other information that will help us debug and reproduce the issue, including stack traces, system/environment information, and screenshots

**Please do not include passwords or any personally identifiable information in your bug report and sample code.**

## Fixing Bugs

We welcome pull requests to fix bugs!

If you see a bug report that you'd like to fix, please feel free to do so.
Following the directions and guidelines described in the "Adding New Features"
section below, you may create bugfix branches and send us pull requests.

## Adding New Features

If you have an idea for a new feature, it's a good idea to check out our
[issues](https://github.com/eclipxe13/micro-catalog/issues) or active
[pull requests](https://github.com/eclipxe13/micro-catalog/pulls)
first to see if we are being working on the feature.
If not, feel free to submit an issue first, asking whether the feature is beneficial to the project.
This will save you from doing a lot of development work only to have your feature rejected.
We don't enjoy rejecting your hard work, but some features just don't fit with the goals of the project.

When you do begin working on your feature, here are some guidelines to consider:

* Your pull request description should clearly detail the changes you have made.
* Follow our code style using `squizlabs/php_codesniffer` and `friendsofphp/php-cs-fixer`.
* Please **write tests** for any new features you add.
* Please **ensure that tests pass** before submitting your pull request. Running the tests locally will help save time.
* We have GitHub Actions automatically running tests for pull requests.
* **Use topic/feature branches.** Please do not ask us to pull from your main branch.
* **Submit one feature per pull request.** If you have multiple features you wish to submit, please break them up into separate pull requests.
* **Send coherent history**. Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before submitting.

## Installing development tools

This project uses different development tools to ensure code style, test and quality (using code analyzers).

```shell
# install project direct dependencies
composer update

# install development tools dependencies (using phive)
phive update
```

## Check the code style

If you are having issues with coding standars use `php-cs-fixer` and `phpcbf`

```shell
# using composer
composer dev:fix-style

# or using tools individually
tools/php-cs-fixer fix -v
tools/phpcbf -sp
```

## Running Tests

The following tests must pass before we will accept a pull request.
If any of these do not pass, it will result in a complete build failure.
Before you can run these, be sure to `composer install` or `composer update`.

```shell
# using composer
composer dev:build

# or using tools individually
tools/phpcs -sp
tools/php-cs-fixer fix -v --dry-run
vendor/bin/phpunit --testdox
tools/phpstan analyze
tools/psalm
tools/infection --show-mutations
```

## Running GitHub Actions locally

You can use [`act`](https://github.com/nektos/act) to run your GitHub Actions locally.
As documented in [`actions/setup-php-action`](https://github.com/marketplace/actions/setup-php-action#local-testing-setup)
you will need to execute the command as:

```shell
act -P ubuntu-latest=shivammathur/node:latest
```
