diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 61a483bd..f47ea4f9 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,3 +1,5 @@ + + # What kind of change does this PR introduce? eg: Bug fix, feature, docs update, ... diff --git a/.github/workflows/pr-quality.yml b/.github/workflows/pr-quality.yml deleted file mode 100644 index 3fdc958b..00000000 --- a/.github/workflows/pr-quality.yml +++ /dev/null @@ -1,52 +0,0 @@ -name: PR Quality - -permissions: - contents: read - issues: read - pull-requests: write - -on: - pull_request_target: - types: [opened, reopened] - -jobs: - anti-slop: - runs-on: ubuntu-latest - steps: - - uses: peakoss/anti-slop@v0 - with: - # Overall - max-failures: 3 - - # Other - require-maintainer-can-modify: true - max-negative-reactions: 3 - require-conventional-title: true - - # Description - max-emoji-count: 2 - max-code-references: 3 - blocked-terms: "Generated with Claude Code,Generated with Codex" - - # PR Template - require-pr-template: true - strict-pr-template-sections: "What kind of change does this PR introduce?,Why was this change needed?,Checklist:" - optional-pr-template-sections: "Other information:" - max-additional-pr-template-sections: 2 - - # User - detect-spam-usernames: true - min-account-age: 30 - max-daily-forks: 5 - min-profile-completeness: 4 - - # Exemptions - exempt-author-association: "OWNER,MEMBER,COLLABORATOR" - exempt-users: "nevo-david,egelhaus" - exempt-bots: "postiz-agent[bot]" - - # Actions - exempt-label: "exempt" - close-pr: true - failure-add-pr-labels: "spam" - failure-pr-message: "This PR has been marked as Spam, please re-open if this is a mistake." diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 960e6f34..344daa29 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,6 +6,10 @@ Contributions are welcome - code, docs, whatever it might be! If this is your fi The main documentation site has a [developer guide](https://docs.postiz.com/developer-guide) . That guide provides you a good understanding of the project structure, and how to setup your development environment. Read this document after you have read that guide. This document is intended to provide you a good understanding of how to submit your first contribution. +## Apply in the contribution form + +To submit your contribution, please fill out the [contribution form](https://contribute.egelhaus.de/p/postiz). This helps us evaluate whether your contribution is a good fit for the project. We will review your submission and get back to you as soon as possible. + ## Write code with others This is an open source project, with an open and welcoming community that is always keen to welcome new contributors. We recommend the two best ways to interact with the community are: