-
Notifications
You must be signed in to change notification settings - Fork 154
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
build: add patch code of conduct workflow
- Loading branch information
Showing
3 changed files
with
66 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
name: Patch Code of Conduct | ||
on: [push] | ||
|
||
jobs: | ||
main_job: | ||
runs-on: ubuntu-latest | ||
name: Test Action | ||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v3 | ||
with: | ||
persist-credentials: false | ||
- name: Patch CoC | ||
uses: pkgjs/[email protected] | ||
with: | ||
base_url: 'UPDATE_THIS' | ||
template_url: 'https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md' | ||
patch_file_path: './conduct/artifacts/CODE_OF_CONDUCT_PATCH' | ||
output_file_path: './CODE_OF_CONDUCT.md' | ||
- uses: gr2m/create-or-update-pull-request-action@v1 | ||
env: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
with: | ||
body: "Applied the patch to the base Code of Conduct." | ||
commit-message: 'doc: update Code of Conduct' | ||
title: 'doc: update Code of Conduct' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
The OpenJS Foundation and its member projects use [Contributor Covenant v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct) as their code of conduct. The full text is included [below](#contributor-covenant-code-of-conduct-v20) in English, and [translations](https://www.contributor-covenant.org/translations) are available on the Contributor Covenant website. | ||
|
||
## Commitment | ||
|
||
All recipients of reports commit to: | ||
|
||
- maintain the confidentiality with regard to the reporter and victim of an incident, and | ||
- participate in the path for escalation as outlined in the section on Escalation when required. | ||
|
||
## Report an issue in a project | ||
|
||
1. To report an issue in one of the projects listed below, please use the method provided. The project itself is responsible for managing these reports. | ||
* **AMP Project:** <[email protected]> | ||
* **Appium:** email maintainers | ||
* **Electron:** <[email protected]> | ||
* **Express.js:** <[email protected]> | ||
* **Fastify:** <[email protected]> or <[email protected]> | ||
* **HospitalRun:** <[email protected]> | ||
* **LoopBack** <[email protected]> | ||
* **Node.js:** <[email protected]> | ||
* **Node-RED:** <[email protected]> | ||
* **Webdriver.io:** [contact TSC reps](https://github.com/webdriverio/webdriverio/blob/HEAD/AUTHORS.md) | ||
* **Webhint:** <[email protected]> | ||
2. For every other OpenJS Foundation project, please email <[email protected]>. The Cross Project Council (CPC) is responsible for managing these reports. | ||
|
||
|
||
## Report an issue in a space managed by the foundation | ||
|
||
For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization or an live event such as a conferences, email <[email protected]>. The Cross Project Council (CPC) is responsible for managing these reports. | ||
|
||
## Escalate an issue | ||
|
||
The OpenJS Foundation maintains a [Code of Conduct Panel (CoCP)](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/conduct/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md#code-of-conduct-panel). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled. | ||
|
||
In order to escalate to the CoCP, email <[email protected]>. | ||
|
||
## More Info | ||
|
||
For more information, refer to the full | ||
[Code of Conduct governance document](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/conduct/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md). |
Empty file.