From a34e30ac5263f700dc444e96d217fadb04100904 Mon Sep 17 00:00:00 2001 From: hackerman <3372410+aeneasr@users.noreply.github.com> Date: Fri, 2 Oct 2020 18:04:58 +0200 Subject: [PATCH] chore: update repository templates (#546) --- .github/workflows/closed_references.yml | 9 ++++++--- .github/workflows/labels.yml | 1 + .github/workflows/milestone.yml | 1 + .github/workflows/stale.yml | 1 + .reference-ignore | 3 +++ CONTRIBUTING.md | 18 ++++++++---------- SECURITY.md | 1 - docs/docs/contributing.md | 18 ++++++++---------- 8 files changed, 28 insertions(+), 24 deletions(-) create mode 100644 .reference-ignore diff --git a/.github/workflows/closed_references.yml b/.github/workflows/closed_references.yml index 5728337d05..ebafc8a71a 100644 --- a/.github/workflows/closed_references.yml +++ b/.github/workflows/closed_references.yml @@ -12,13 +12,16 @@ on: jobs: find_closed_references: + if: github.repository_owner == 'ory' runs-on: ubuntu-latest 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' - issueLabels: upstream + issueLabels: upstream,good first issue,help wanted issueLimit: ${{ github.event.inputs.issueLimit || '5' }} diff --git a/.github/workflows/labels.yml b/.github/workflows/labels.yml index 4ad85dbec6..c470ddc82f 100644 --- a/.github/workflows/labels.yml +++ b/.github/workflows/labels.yml @@ -8,6 +8,7 @@ on: jobs: milestone: + if: github.repository_owner == 'ory' name: Synchronize Issue Labels runs-on: ubuntu-latest steps: diff --git a/.github/workflows/milestone.yml b/.github/workflows/milestone.yml index 5b5e7f97a4..fb47e4a78f 100644 --- a/.github/workflows/milestone.yml +++ b/.github/workflows/milestone.yml @@ -7,6 +7,7 @@ on: jobs: milestone: + if: github.repository_owner == 'ory' name: Generate and Publish Milestone Document runs-on: ubuntu-latest steps: diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 117f8469ba..3017170dbe 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -6,6 +6,7 @@ on: jobs: stale: + if: github.repository_owner == 'ory' runs-on: ubuntu-latest steps: - uses: actions/stale@v3 diff --git a/.reference-ignore b/.reference-ignore new file mode 100644 index 0000000000..eee2a89c2e --- /dev/null +++ b/.reference-ignore @@ -0,0 +1,3 @@ +**/node_modules +docs +CHANGELOG.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3ca8b8d18e..1e946aa9f6 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 8bae0531cd..70f1ef4ddb 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) diff --git a/docs/docs/contributing.md b/docs/docs/contributing.md index 33f4d64a41..925fc2fc78 100644 --- a/docs/docs/contributing.md +++ b/docs/docs/contributing.md @@ -13,13 +13,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) @@ -148,23 +146,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