FM / phpspreadsheet

/home/techb158/immovalet.com/vendor/phpoffice/phpspreadsheet/

/home/techb158/immovalet.com/vendor/phpoffice/phpspreadsheet

Name	Size	Mode	Actions
src/	-	0755	rm
.phpcs.xml.dist	752	0644	edit dl rm
CHANGELOG.md	49544	0644	edit dl rm
composer.json	3258	0644	edit dl rm
CONTRIBUTING.md	1166	0644	edit dl rm
LICENSE	1079	0644	edit dl rm
phpstan-baseline.neon	339223	0644	edit dl rm
phpstan.neon.dist	2107	0644	edit dl rm
README.md	2341	0644	edit dl rm

Edit: /home/techb158/immovalet.com/vendor/phpoffice/phpspreadsheet/CONTRIBUTING.md (1166B)

# Want to contribute?

If you would like to contribute, here are some notes and guidelines:

- All new development happens on feature/fix branches, and are then merged to the `master` branch once stable; so the `master` branch is always the most up-to-date, working code
 - Tagged releases are made from the `master` branch
 - If you are going to be submitting a pull request, please fork from `master`, and submit your pull request back as a fix/feature branch referencing the GitHub issue number
 - Code style might be automatically fixed by `composer fix`
 - All code changes must be validated by `composer check`
 - [Helpful article about forking](https://help.github.com/articles/fork-a-repo/ "Forking a GitHub repository")
 - [Helpful article about pull requests](https://help.github.com/articles/using-pull-requests/ "Pull Requests")

## How to release

1. Complete CHANGELOG.md and commit
2. Create an annotated tag
    1. `git tag -a 1.2.3`
    2. Tag subject must be the version number, eg: `1.2.3`
    3. Tag body must be a copy-paste of the changelog entries
3. Push tag with `git push --tags`, GitHub Actions will create a GitHub release automatically

# Want to contribute? If you would like to contribute, here are some notes and guidelines: - All new development happens on feature/fix branches, and are then merged to the `master` branch once stable; so the `master` branch is always the most up-to-date, working code - Tagged releases are made from the `master` branch - If you are going to be submitting a pull request, please fork from `master`, and submit your pull request back as a fix/feature branch referencing the GitHub issue number - Code style might be automatically fixed by `composer fix` - All code changes must be validated by `composer check` - [Helpful article about forking](https://help.github.com/articles/fork-a-repo/ "Forking a GitHub repository") - [Helpful article about pull requests](https://help.github.com/articles/using-pull-requests/ "Pull Requests") ## How to release 1. Complete CHANGELOG.md and commit 2. Create an annotated tag 1. `git tag -a 1.2.3` 2. Tag subject must be the version number, eg: `1.2.3` 3. Tag body must be a copy-paste of the changelog entries 3. Push tag with `git push --tags`, GitHub Actions will create a GitHub release automatically