diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 3a830d5c..6fb51639 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -20,10 +20,6 @@ Steps to reproduce the behavior: A clear and concise description of what you expected to happen. -**Expected behavior** - -A clear and concise description of what you expected to happen. - **Environment** - Version: v1.2.3, git sha hash diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index bd9fd963..13448cf5 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -3,14 +3,20 @@ name: Feature request about: Suggest an idea for this project --- -**Is your feature request related to a problem? Please describe.** A clear and -concise description of what the problem is. Ex. I'm always frustrated when [...] +**Is your feature request related to a problem? Please describe.** -**Describe the solution you'd like** A clear and concise description of what you -want to happen. +A clear and concise description of what the problem is. Ex. I'm always +frustrated when [...] -**Describe alternatives you've considered** A clear and concise description of -any alternative solutions or features you've considered. +**Describe the solution you'd like** -**Additional context** Add any other context or screenshots about the feature -request here. +A clear and concise description of what you want to happen. + +**Describe alternatives you've considered** + +A clear and concise description of any alternative solutions or features you've +considered. + +**Additional context** + +Add any other context or screenshots about the feature request here. diff --git a/.github/workflows/closed_references.yml b/.github/workflows/closed_references.yml index 5728337d..3e21a743 100644 --- a/.github/workflows/closed_references.yml +++ b/.github/workflows/closed_references.yml @@ -16,9 +16,12 @@ jobs: name: Find closed references steps: - uses: actions/checkout@v2 - - uses: ory/closed-reference-notifier@v1.1.4 + - uses: actions/setup-node@v2-beta + with: + node-version: '14' + - uses: ory/closed-reference-notifier@v1 with: token: ${{ secrets.GITHUB_TOKEN }} - ignore: '.git,**/node_modules,docs,CHANGELOG.md,.bin,*.md' + ignore: ".git,**/node_modules,docs,CHANGELOG.md,.bin,*.md" issueLabels: upstream issueLimit: ${{ github.event.inputs.issueLimit || '5' }} diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3ca8b8d1..1e946aa9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,13 +8,11 @@ https://github.com/ory/meta/blob/master/templates/repository/CONTRIBUTING.md --> - # Contributing to ORY {{Project}} - - [Introduction](#introduction) - [Contributing Code](#contributing-code) - [Disclosing vulnerabilities](#disclosing-vulnerabilities) @@ -143,23 +141,23 @@ please include a note in your commit message explaining why. ## How We Organize Our Work -All repositories in the [ORY organization](https://github.com/ory) have their issues and pull requests +All repositories in the [ORY organization](https://github.com/ory) have their issues and pull requests monitored in the [ORY Monitoring Board](https://github.com/orgs/ory/projects/9). This allows for a transparent backlog of unanswered issues and pull requests across the ecosystem from those who are allowed to merge pull requests to the main branch. The process is as follows: -1. *Cards* represent open issues and pull requests and are automatically assigned to the **Triage** column if -the author is not one of the maintainers and no maintainer has answered yet. -2. A maintainer assigns the issue or pull request to someone or adds the label *help wanted* -which moves the card to **Requires Action**. +1. _Cards_ represent open issues and pull requests and are automatically assigned to the **Triage** column if + the author is not one of the maintainers and no maintainer has answered yet. +2. A maintainer assigns the issue or pull request to someone or adds the label _help wanted_ + which moves the card to **Requires Action**. 3. If a maintainer leaves a comment or review, the card moves to **Pending Reply**, implying that -the original author needs to do something (e.g. implement a change, explain something in more detail, ...). + the original author needs to do something (e.g. implement a change, explain something in more detail, ...). 4. If a non-maintainer pushes changes to the pull request or leaves a comment, the card moves -back to **Requires Action**. + back to **Requires Action**. 5. If a card stays inactive for 60 days or more days, we assume that public interest in the issue -or change has waned, **archiving** the card. + or change has waned, **archiving** the card. 6. If the issue is closed or the pull request merged or closed, the card is **archived** as well. We try our best to answer all issues and review all pull requests and hope that this transparent way diff --git a/SECURITY.md b/SECURITY.md index 8bae0531..70f1ef4d 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -11,7 +11,6 @@ https://github.com/ory/meta/blob/master/templates/repository/SECURITY.md - - [Security Policy](#security-policy) - [Supported Versions](#supported-versions) - [Reporting a Vulnerability](#reporting-a-vulnerability)