Parse and publish hashtags in notes when posting #3515
Workflow file for this run
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
| # via https://github.com/marketplace/actions/cla-assistant-lite | |
| name: "CLA Assistant" | |
| on: | |
| issue_comment: | |
| types: [created] | |
| pull_request_target: | |
| types: [opened,closed,synchronize] | |
| merge_group: | |
| types: [checks_requested] | |
| # explicitly configure permissions, in case your GITHUB_TOKEN workflow permissions are set to read-only in repository settings | |
| permissions: | |
| actions: write | |
| contents: write | |
| 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 the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target' | |
| uses: contributor-assistant/[email protected] | |
| 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: 'signatures/version1/cla.json' | |
| path-to-document: 'https://github.com/planetary-social/nos/blob/main/CLA.md' # e.g. a CLA or a DCO document | |
| # branch should not be protected | |
| branch: 'cla-signatures' | |
| allowlist: crowdin-bot,crowdin-bot[bot],github-actions,app/github-actions,github-actions[bot] | |
| # 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 submission -- we really appreciate it! We'd love it if you'd sign our [Contributor License Agreement](https://github.com/planetary-social/nos/blob/main/CLA.md) so we can accept your contribution. You can sign the CLA by copying the text below, pasting it in the **Add a comment** text field at the bottom of this pull request, and clicking the **Comment** button to post it." | |
| #custom-pr-sign-comment: 'The signature to be committed in order to sign the CLA' | |
| #custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.' | |
| 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 |