Suspended Server Does Not Automatically Unsuspend After Adding User Credits #98
This file contains hidden or 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
| name: "CLA Assistant" | |
| on: | |
| issue_comment: | |
| types: [created] | |
| pull_request_target: | |
| types: [opened,closed,synchronize] | |
| # explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings | |
| permissions: | |
| actions: write | |
| contents: write # this can be 'read' if the signatures are in remote repository | |
| pull-requests: write | |
| statuses: write | |
| jobs: | |
| CLAAssistant: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: "CLA Assistant" | |
| if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read and agree to the CLA.') || github.event_name == 'pull_request_target' | |
| uses: contributor-assistant/github-action@v2.6.1 | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| # the below token should have repo scope and must be manually added by you in the repository's secret | |
| # This token is required only if you have configured to store the signatures in a remote repository/organization | |
| # PERSONAL_ACCESS_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }} | |
| with: | |
| path-to-signatures: 'cla-signatures.json' | |
| path-to-document: 'https://github.com/CtrlPanel-gg/panel/blob/development/CONTRIBUTOR_LICENSE_AGREEMENT' # e.g. a CLA or a DCO document | |
| # branch should not be protected | |
| branch: 'cla-signatures' | |
| allowlist: 1day2die | |
| # the followings are the optional inputs - If the optional inputs are not given, then default values will be taken | |
| #remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository) | |
| #remote-repository-name: enter the remote repository name where the signatures should be stored (Default is storing the signatures in the same repository) | |
| #create-file-commit-message: 'For example: Creating file for storing CLA Signatures' | |
| #signed-commit-message: 'For example: $contributorName has signed the CLA in $owner/$repo#$pullRequestNo' | |
| custom-notsigned-prcomment: | | |
| 👋 Thank $you for your contribution to CtrlPanel! | |
| Before we can review and merge your pull request, we require all contributors to sign our **Contributor License Agreement (CLA)**. This ensures the project can remain open source and that contributions can be properly licensed. | |
| 📄 Please read the CLA here: https://github.com/CtrlPanel-gg/panel/blob/development/CONTRIBUTOR_LICENSE_AGREEMENT | |
| To confirm your agreement, post a comment on this pull request containing exactly the following: | |
| custom-pr-sign-comment: 'I have read and agree to the CLA.' | |
| custom-allsigned-prcomment: | | |
| All contributors have signed the CLA! ✅ | |
| Thank you for taking the time to complete this step. We'll now proceed with reviewing your pull request. We appreciate your contribution to Ctrlpanel! 🙌 | |
| #lock-pullrequest-aftermerge: false - if you don't want this bot to automatically lock the pull request after merging (default - true) | |
| #use-dco-flag: true - If you are using DCO instead of CLA |