Explorar el Código

Merge branch 'master' into master

pull/719/head
Alexander Kartavenko hace 1 año
padre
commit
9e2159cfe2
No account linked to committer's email address
Se han modificado 5 ficheros con 465 adiciones y 518 borrados
  1. 23
    0
      .github/workflows/awesomebot.yml
  2. 0
    9
      .travis.yml
  3. 0
    65
      .varci.yml
  4. 10
    9
      CONTRIBUTING.md
  5. 432
    435
      README.md

+ 23
- 0
.github/workflows/awesomebot.yml Ver fichero

@@ -0,0 +1,23 @@
1
+name: Awesome Bot
2
+on:
3
+  push:
4
+    branches:
5
+      - master
6
+jobs:
7
+  build:
8
+    runs-on: ubuntu-latest
9
+    steps:
10
+    - uses: actions/checkout@v1
11
+    - name: Set up Ruby
12
+      uses: actions/setup-ruby@v1
13
+      with:
14
+        ruby-version: 2.7.x
15
+    - name: Install Awesome Bot
16
+      run: gem install awesome_bot
17
+    - name: Run Awesome Bot
18
+      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
19
+    - uses: actions/upload-artifact@v1
20
+      if: failure()
21
+      with:
22
+        name: ab-results
23
+        path: ab-results-README.md-filtered.json

+ 0
- 9
.travis.yml Ver fichero

@@ -1,9 +0,0 @@
1
-language: ruby
2
-rvm:
3
-  - 2.2
4
-before_script:
5
-  - gem install awesome_bot
6
-script:
7
-  - awesome_bot README.md --white-list igor.io,symfony,toranproxy.com
8
-notifications:
9
-  email: false

+ 0
- 65
.varci.yml Ver fichero

@@ -1,65 +0,0 @@
1
-ruleset:
2
-
3
-  body_link:
4
-    name: "Pull requests that add links should also include them in the body"
5
-    events: [ pull_request ]
6
-    when:
7
-      - action = "opened"
8
-      - files = ["README.md"]
9
-      - deletions = 0
10
-      - not (body_links.added contains diff_links.added)
11
-    comment: |
12
-      This pull request adds the following suggestion:
13
-
14
-      {{ diff.added.0 }}
15
-
16
-  broken_link:
17
-    name: "Pull request diff contains broken links"
18
-    events: [ pull_request ]
19
-    when:
20
-      - action = "opened"
21
-      - count(diff_links.broken) > 0
22
-    comment: >
23
-      @{{ user.login }}, at least one of the links in the pull request diff was
24
-      reported as broken:
25
-
26
-      - {{ diff_links.broken.0 }}
27
-
28
-  missing_link:
29
-    name: "Suggestions should include a link"
30
-    events: [ pull_request ]
31
-    when:
32
-      - action = "opened"
33
-      - files = ["README.md"]
34
-      - deletions = 0
35
-      - additions = 1
36
-      - count(grep("/^\* /", diff.added)) = 1
37
-      - count(diff_links.added) != 1
38
-    comment: >
39
-      @{{ user.login }}, it looks like you have added a new suggestion to the
40
-      `README.md` file but haven't linked to the project. Please update the
41
-      `README.md` to also link to the project, thanks!
42
-
43
-  multiple_additions:
44
-    name: "Pull request should only suggest one addition at a time"
45
-    events: [ pull_request ]
46
-    comment: |
47
-      @{{ user.login }}, it looks like you are trying to add multiple suggestions in a single pull request.
48
-
49
-      If so, please split these into multiple pull requests so each item's inclusion in the list can be discussed separately.
50
-    when:
51
-      - action = "opened"
52
-      - files = ["README.md"]
53
-      - deletions = 0
54
-      - count(grep("/^\* /", diff.added)) > 1
55
-
56
-  needs_explanation:
57
-    name: 'Pull request bodies should have a detailed explanation'
58
-    events: [ pull_request ]
59
-    label: 'needs: explanation'
60
-    when:
61
-      - action = "opened"
62
-      - length(body) < 25
63
-    message: >
64
-      @{{ user.login }}, please update the pull request body with a description
65
-      of what you are adding or changing (of at least 25 characters).

+ 10
- 9
CONTRIBUTING.md Ver fichero

@@ -1,26 +1,27 @@
1 1
 # Contribution Guidelines
2
-Unfortunately, not every library, tool or framework can be considered for inclusion. The aim of Awesome PHP is to be a concise list of noteworthy and interesting software written in modern PHP. Therefore, suggested software should: 
2
+Unfortunately, not every library, tool or framework can be considered for inclusion. The aim of Awesome PHP is to be a concise list of noteworthy and interesting software written in modern PHP. Therefore, suggested software should:
3 3
 
4
-a) Be widely recommended regardless of personal opinion  
5
-b) Well known or discussed within the PHP community  
6
-c) Be unique in its approach or function  
7
-d) Fill a niche gap in the market  
4
+1. Be widely recommended
5
+2. Well known or discussed within the PHP community
6
+3. Be unique in its approach or function
7
+4. Fill a niche gap in the market
8 8
 
9 9
 Self-promotion is frowned upon, so please consider seriously whether your project meets the criteria before opening a pull request, otherwise it may be closed without being reviewed.
10 10
 
11 11
 Also, please ensure your pull request adheres to the following guidelines:
12 12
 
13
-* Software that is PHP 5.5+, Composer-installable, PSR compliant, semantically versioned, united tested and well documented in English is preferred.
14
-* Please search previous suggestions before making a new one, as yours may be a duplicate.
13
+* Software that is PHP 8.0+, Composer-installable, PSR compliant, semantically versioned, unit tested, actively maintained and well documented in English.
14
+* Please search previous suggestions before making a new one, as yours may be a duplicate and will be closed.
15 15
 * Enter a meaningful pull request description.
16
-* Please make an individual commit for each suggestion in a separate pull request.
17 16
 * Put a link to each library in your pull request ticket so it's easier to review.
17
+* Please make an individual commit for each suggestion in a separate pull request.
18 18
 * Use the following format for libraries: \[LIBRARY\]\(LINK\) - DESCRIPTION.
19 19
 * Prefix duplicate library names with their vendor or namespace followed by a space: Foo\Bar would be Foo Bar.
20 20
 * New categories, or improvements to the existing categorisation, are always welcome.
21
-* Please keep descriptions short, simple and unbiased. No buzzwords or marketing jargon. 
21
+* Please keep descriptions short, simple and unbiased. No buzzwords or marketing jargon please.
22 22
 * End all descriptions with a full stop/period.
23 23
 * Check your spelling and grammar.
24 24
 * Make sure your text editor is set to remove trailing whitespace.
25
+* Your entry has been added alphabetically within the category.
25 26
 
26 27
 Thank you for your suggestions!

+ 432
- 435
README.md
La diferencia del archivo ha sido suprimido porque es demasiado grande
Ver fichero


Loading…
Cancelar
Guardar