Merge branch 'master' into patch-1

This commit is contained in:
Alexander Schranz 2024-06-10 16:01:27 +02:00 committed by GitHub
commit ea2a364353
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
6 changed files with 297 additions and 293 deletions

10
.editorconfig Normal file
View File

@ -0,0 +1,10 @@
; This file is for unifying the coding style for different editors and IDEs.
; More information at https://editorconfig.org
root = true
[*]
indent_style = space
indent_size = 2
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true

View File

@ -3,19 +3,22 @@ on:
push:
branches:
- master
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: Set up Ruby
uses: actions/setup-ruby@v1
- uses: actions/checkout@v4
- uses: ruby/setup-ruby@v1
with:
ruby-version: 2.7.x
ruby-version: '2.7'
- name: Install Awesome Bot
run: gem install awesome_bot
- name: Run Awesome Bot
run: awesome_bot README.md --request-delay 1 --allow-dupe --white-list igor.io,symfony,toranproxy.com,vagrantup.com,3v4l.org,voicesoftheelephpant.com,drupal.org,oreilly.com
run: awesome_bot README.md --request-delay 1 --allow-dupe --white-list igor.io,symfony,toranproxy.com,vagrantup.com,3v4l.org,voicesoftheelephpant.com,drupal.org,oreilly.com,youtube.com,lumen.laravel.com
- uses: actions/upload-artifact@v1
if: failure()
with:

View File

@ -35,7 +35,7 @@ This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community.
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting a project maintainer at awesome-php@josediazgonzalez.com. All
reported by contacting a project maintainer at ziadoz@gmail.com. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. Maintainers are
obligated to maintain confidentiality with regard to the reporter of an

View File

@ -13,9 +13,10 @@ If you provide feedback on a suggested project please be friendly and constructi
## Reviewing
Please work through the following checklist when reviewing a project:
- Tag pull requests with the most relevant label(s).
- Validate URLs work correctly and don't point to anything malicious.
- Ensure suggestions adhere to [CONTRIBUTING](https://github.com/ziadoz/awesome-php/blob/master/CONTRIBUTING.md).
- Validate URLs work correctly and don't point to anything malicious.
- Two approvals per pull request is preferred, but not required.
- Simple pull requests fixing typos, formatting and broken links can be merged with a single approval.
## Enhancements
If you have an idea on how to improve the project, please open a ticket for discussion using the `Enhancement` label. Please dont make any broad or sweeping changes without consulting other collaborators first and reaching a consensus.
@ -23,4 +24,4 @@ If you have an idea on how to improve the project, please open a ticket for disc
## Join
If you want to help out please send an email to my Github username [at] gmail [dot] com with the subject “Awesome PHP Collaborator and a link to your Github account and Ill get back to you as soon as I can (I'm notoriously slow, sorry).
Thank you for taking the time to help out with Awesome PHP, your help is appreciated!
Thank you for taking the time to help out with Awesome PHP, your help is appreciated!

View File

@ -10,15 +10,15 @@ Self-promotion is frowned upon, so please consider seriously whether your projec
Also, please ensure your pull request adheres to the following guidelines:
* Software that is PHP 7.0+, Composer-installable, PSR compliant, semantically versioned, unit tested, actively maintained and well documented in English.
* Please search previous suggestions before making a new one, as yours may be a duplicate.
* Software that is PHP 8.0+, Composer-installable, PSR compliant, semantically versioned, unit tested, actively maintained and well documented in English.
* Please search previous suggestions before making a new one, as yours may be a duplicate and will be closed.
* Enter a meaningful pull request description.
* Please make an individual commit for each suggestion in a separate pull request.
* Put a link to each library in your pull request ticket so it's easier to review.
* Please make an individual commit for each suggestion in a separate pull request.
* Use the following format for libraries: \[LIBRARY\]\(LINK\) - DESCRIPTION.
* Prefix duplicate library names with their vendor or namespace followed by a space: Foo\Bar would be Foo Bar.
* New categories, or improvements to the existing categorisation, are always welcome.
* Please keep descriptions short, simple and unbiased. No buzzwords or marketing jargon.
* Please keep descriptions short, simple and unbiased. No buzzwords or marketing jargon please.
* End all descriptions with a full stop/period.
* Check your spelling and grammar.
* Make sure your text editor is set to remove trailing whitespace.

550
README.md

File diff suppressed because it is too large Load Diff