asyncapi · asyncapi-bot · Jun 23, 2022 · May 10, 2022 · May 10, 2022 · May 10, 2022
@@ -145,7 +145,9 @@
       "profile": "https://waleedashraf.me/",
       "contributions": [
         "talk",
-        "ideas"
+        "ideas",
+        "doc",
+        "example"
       ]
     },
     {
@@ -215,7 +217,12 @@
       "profile": "https://github.com/magicmatatjahu",
       "contributions": [
         "review",
-        "ideas"
+        "ideas",
+        "question",
+        "bug",
+        "doc",
+        "example",
+        "maintenance"
       ]
     },
     {
@@ -224,7 +231,11 @@
       "avatar_url": "https://avatars.githubusercontent.com/u/193286?v=4",
       "profile": "https://vladimirgorej.com/",
       "contributions": [
-        "doc"
+        "doc",
+        "bug",
+        "example",
+        "ideas",
+        "review"
       ]
     },
     {
@@ -271,7 +282,12 @@
       "contributions": [
         "review",
         "ideas",
-        "question"
+        "question",
+        "blog",
+        "bug",
+        "doc",
+        "example",
+        "maintenance"
       ]
     },
     {
@@ -329,6 +345,40 @@
       "contributions": [
         "doc"
       ]
+    },
+    {
+      "login": "danielkocot",
+      "name": "Daniel Kocot",
+      "avatar_url": "https://avatars.githubusercontent.com/u/466609?v=4",
+      "profile": "https://danielkocot.github.io/",
+      "contributions": [
+        "doc",
+        "example",
+        "ideas"
+      ]
+    },
+    {
+      "login": "sekharbans-ebay",
+      "name": "sekharbans-ebay",
+      "avatar_url": "https://avatars.githubusercontent.com/u/66145510?v=4",
+      "profile": "https://github.com/sekharbans-ebay",
+      "contributions": [
+        "doc",
+        "example",
+        "ideas"
+      ]
+    },
+    {
+      "login": "damaru-inc",
+      "name": "Michael Davis",
+      "avatar_url": "https://avatars.githubusercontent.com/u/3926925?v=4",
+      "profile": "http://www.damaru.com/",
+      "contributions": [
+        "bug",
+        "doc",
+        "example",
+        "ideas"
+      ]
     }
   ],
   "commitConvention": "none"

@@ -9,7 +9,7 @@ module.exports = (givenSpec) => {
   const startingLine = "## Table of Contents\n";
   const endingLine = "<!-- /TOC -->\n";
 
-  const specFile = fs.readFileSync(`./website/pages/docs/specifications/${givenSpec}.md`);
+  const specFile = fs.readFileSync(`./website/pages/docs/reference/specification/${givenSpec}.md`);
 
   const startingIndex = specFile.indexOf(startingLine);
   const endingIndex = specFile.indexOf(endingLine);
@@ -21,5 +21,5 @@ module.exports = (givenSpec) => {
   const firstHalf = specFile.slice(0, startingIndex);
   const secondHalf = specFile.slice(endingIndex + endingLine.length);
   const specWithoutToc = `${firstHalf}${secondHalf}`;
-  fs.writeFileSync(`./website/pages/docs/specifications/${givenSpec}.md`, specWithoutToc);
+  fs.writeFileSync(`./website/pages/docs/reference/specification/${givenSpec}.md`, specWithoutToc);
 }
@@ -9,6 +9,7 @@ on:
 
 jobs:
   identify-orphans:
+    if: startsWith(github.repository, 'asyncapi/')
     name: Find orphans and notify
     runs-on: ubuntu-latest
     steps:

@@ -20,13 +20,14 @@ on:
 
 jobs:
   autoupdate-for-bot:
+    if: startsWith(github.repository, 'asyncapi/')
     name: Autoupdate autoapproved PR created in the upstream
     runs-on: ubuntu-latest
     steps:
       - name: Autoupdating
         uses: docker://chinthakagodawita/autoupdate-action:v1
         env:
-          GITHUB_TOKEN: '${{ secrets.GH_TOKEN }}'
+          GITHUB_TOKEN: '${{ secrets.GH_TOKEN_BOT_EVE }}'
           PR_FILTER: "labelled"
           PR_LABELS: "autoupdate"
           PR_READY_STATE: "ready_for_review"

@@ -25,7 +25,7 @@ jobs:
 
             - `/ready-to-merge` or `/rtm` - This comment will trigger automerge of PR in case all required checks are green, approvals in place and do-not-merge label is not added
             - `/do-not-merge` or `/dnm` - This comment will block automerging even if all conditions are met and ready-to-merge label is added
-            - `/autoupdate` or `/au` - This comment will add `autoupdate` label to the PR and keeps your PR up-to-date to the target branch's future changes. Unless there is a merge conflict.
+            - `/autoupdate` or `/au` - This comment will add `autoupdate` label to the PR and keeps your PR up-to-date to the target branch's future changes. Unless there is a merge conflict or it is a draft PR.
   create_help_comment_issue:
     if: ${{ !github.event.issue.pull_request && contains(github.event.comment.body, '/help') && github.actor != 'asyncapi-bot' }}
     runs-on: ubuntu-latest

@@ -11,6 +11,7 @@ on:
 
 jobs:
   External-link-validation-weekly:
+    if: startsWith(github.repository, 'asyncapi/')
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v3

@@ -38,20 +38,20 @@ jobs:
           script: |
             const fs = require("fs");
 
-            const specFiles = fs.readdirSync("./website/pages/docs/specifications");
+            const specFiles = fs.readdirSync("./website/pages/docs/reference/specification");
 
             const nextRelease = `${{github.event.release.tag_name}}`;
             const prefixRelease = nextRelease.split("-")[0];
 
             for (const filename of specFiles) {
               if (filename.startsWith(prefixRelease)) {
-                fs.unlinkSync(`./website/pages/docs/specifications/${filename}`);
+                fs.unlinkSync(`./website/pages/docs/reference/specification/${filename}`);
               }
             }
       - name: Copy Spec file from Current Repo to Another
         working-directory: ./website
         run: |
-          cp ../spec/spec/asyncapi.md ./pages/docs/specifications/${{github.event.release.tag_name}}.md
+          cp ../spec/spec/asyncapi.md ./pages/docs/reference/specification/${{github.event.release.tag_name}}.md
       - name: Remove Table of Contents from Spec
         uses: actions/github-script@v4
         with:
@@ -71,7 +71,7 @@ jobs:
             const endingLine = "# LATEST-SPEC-REDIRECTION:END";
 
             const releaseVersion = `${{github.event.release.tag_name}}`;
-            const redirectLine = `/docs/specifications/latest /docs/specifications/${releaseVersion} 302!\n`;
+            const redirectLine = `/docs/reference/specification/latest /docs/reference/specification/${releaseVersion} 302!\n`;
 
             const redirectFile = fs.readFileSync("./website/public/_redirects", "utf-8");
 
@@ -139,7 +139,7 @@ jobs:
 
             const releaseVersionWithoutV = releaseVersion.slice(1);
 
-            const redirectLine = `/docs/specifications/${releaseVersionWithoutV} /docs/specifications/${releaseVersion} 302!\n`;
+            const redirectLine = `/docs/reference/specification/${releaseVersionWithoutV} /docs/reference/specification/${releaseVersion} 302!\n`;
 
             const redirectFile = fs.readFileSync("./website/public/_redirects", "utf-8");
 

@@ -9,6 +9,7 @@ on:
 
 jobs:
   stale:
+    if: startsWith(github.repository, 'asyncapi/')
     name: Mark issue or PR as stale
     runs-on: ubuntu-latest
     steps:

@@ -41,7 +41,7 @@ jobs:
       - name: Copy Spec file from Current Repo to Another
         working-directory: ./website
         run: |
-          cp ../spec/spec/asyncapi.md ./pages/docs/specifications/${{ steps.latest_version.outputs.latest_tag }}.md
+          cp ../spec/spec/asyncapi.md ./pages/docs/reference/specification/${{ steps.latest_version.outputs.latest_tag }}.md
       - name: Remove Table of Contents from Spec
         uses: actions/github-script@v4
         with:

@@ -1,7 +1,9 @@
 ---
 branches:
 - master
-- name: 2022-04-release
+- name: next-spec
+  prerelease: true
+- name: next-major-spec
   prerelease: true
 plugins:
 - - "@semantic-release/commit-analyzer"

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at fmvilas@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/