Adding path level tagging

.github/workflows/convert-examples-to-json.yaml

@@ -0,0 +1,50 @@
+name: convert-examples-to-json
+
+# author: @MikeRalphson / @cebe
+# issue: https://github.com/OAI/OpenAPI-Specification/issues/1385
+
+#
+# This workflow updates the *.json files in the examples/v3.x directories,
+# when the corresponding *.yaml files change.
+# JSON example files are automatically generated from the YAML example files.
+# Only the YAML files should be adjusted manually.
+#
+
+# run this on push to master
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  yaml2json:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v1 # checkout repo content
+
+    - name: Install dependencies
+      run: npm i
+
+    - name: convert YAML examples to JSON
+      run: find examples/v3* -type f -name "*.yaml" | xargs node scripts/yaml2json/yaml2json.js
+
+    - name: git diff
+      run: |
+        git add examples/**/*.json
+        git --no-pager -c color.diff=always diff --staged
+
+    - name: Create Pull Request
+      uses: peter-evans/create-pull-request@v1
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        branch-suffix: none
+        branch: update-json-examples
+        title: Update JSON example files
+        commit-message: Update JSON example files
+        body: |
+          This pull request is automatically triggered by GitHub action `convert-examples-to-json`.
+
+          The examples/v3.* YAML files have changed, so the JSON files are automatically being recreated.
+

.github/workflows/validate-markdown.yaml

@@ -0,0 +1,27 @@
+name: validate-markdown
+
+# Author: @MikeRalphson
+# Issue: https://github.com/OAI/OpenAPI-Specification/issues/2130
+
+#
+# This workflow validates files in the versions directory matching 3.*.md
+# Versions before 3.0 are not validated, as they contain linking errors
+# where it is not currently planned to go back and fix them
+#
+
+# run this on push to any branch and creation of pull-requests
+on: [push, pull_request]
+
+jobs:
+  mdv:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v1 # checkout repo content
+    - uses: actions/setup-node@v1 # setup Node.js
+      with:
+        node-version: '12.x'
+    - name: Validate markdown
+      run: npx mdv versions/3.*.md
+

.gitignore

@@ -5,4 +5,5 @@
 target
 atlassian-ide-plugin.xml
 node_modules/
+package-lock.json
 Gemfile.lock

CODE_OF_CONDUCT.md

@@ -0,0 +1,118 @@
+Code of Conduct
+===============
+
+OpenAPI Initiative Code of Conduct
+
+*The Linux Foundation*
+
+*Effective November 24, 2020*
+
+The OpenAPI Initiative (OAI) is an open source Linux Foundation project
+and home of the OpenAPI Specification (OAS) released under the Apache
+2.0 license. As contributors, maintainers, and participants in this
+project, we want to foster an open and welcoming environment. We 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,
+education, socio-economic status, nationality, personal appearance,
+race, religion, or sexual identity and orientation.
+
+Our Standards
+-------------
+
+Examples of behaviors that contribute 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
+
+-   Assuming the best intent from others
+
+Examples of unacceptable behavior by participants include:
+
+-   The use of sexualized language or imagery and unwelcome sexual attention or advances
+
+-   Making unsolicited, insulting or derogatory comments, including personal (i.e., ad hominem) or political attacks to create conflict (e.g., trolling)
+
+-   Public or private harassment
+
+-   Publishing others' private information, such as a physical or electronic address, without explicit permission (e.g., doxxing)
+
+-   Threatening, offensive, harmful comments, or behavior
+
+-   Other conduct which could reasonably be considered inappropriate in a professional setting
+
+Our Responsibilities
+--------------------
+
+The Code of Conduct Committee is responsible for clarifying the
+standards of acceptable behavior and is expected to take appropriate and
+fair corrective action in response to any instances of unacceptable
+behavior.
+
+Scope
+-----
+
+This Code of Conduct applies to OAI project spaces, as well as
+interactions in public spaces. Project spaces include, but are not
+limited to, official OAI code repositories, Slack, mailing lists,
+meetings, and events. Public spaces may include venues where an
+individual is representing the project or its community. Examples of
+this include a community member's email communication, forum posts,
+social media activity, or acting as a representative at an online or
+offline event. In addition, violations of this code of conduct outside
+of these spaces may affect a person's ability to participate in them.
+
+Enforcement
+-----------
+
+To report instances of abuse, harassment, or otherwise unacceptable
+behavior, contact
+[conduct\@openapis.org](mailto:conduct@openapis.org). **We
+are committed to maintaining the confidentiality of anyone reporting an
+incident**. The Code of Conduct Committee will review and investigate
+all complaints, responding as deemed necessary and appropriate to the
+circumstances. For incidents relating to offline events, we aim to
+respond to reports within 24 hours, and for incidents relating to online
+activities, we aim to respond to reports within 7 days.
+
+The Code of Conduct Committee has 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
+take other appropriate action as deemed necessary for behaviors contrary
+to the standards listed above. In the case of offline or in-person
+events, if a participant engages in behavior that is not aligned to this
+Code of Conduct, the committee may take action, such as warning the
+offender, banning the offender from various online spaces (temporary or
+permanent), removing the offender from an event with no refund, or other
+options deemed appropriate.
+
+Further details of specific enforcement policies are currently being
+drafted. When these details are completed we will post updates to our
+website for transparency.
+
+Project maintainers who do not report possible incidents or follow
+responses in good faith may face temporary or permanent repercussions as
+determined by the Code of Conduct Committee.
+
+### Events
+
+Some OpenAPI events are governed by the [Linux Foundation Code of
+Conduct](https://events.linuxfoundation.org/about/code-of-conduct/)
+(E.g. API Specifications Conference) and will be listed on the event
+page. The OAI Code of Conduct is designed to be compatible with the
+above policy and also includes more details on responding to incidents.
+
+### Attribution
+
+This code of conduct is adapted from the [Contributor Covenant, version
+1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct)
+and the [PyCon 2019 Code of
+Conduct](https://us.pycon.org/2019/about/code-of-conduct/).