Formatting

check-cla/action.yml

@@ -125,7 +125,8 @@ runs:
         author: Conda Bot <[email protected]>
         committer: Conda Bot <[email protected]>
         title: 🤖 Add ${{ env.CONTRIBUTOR_LOGIN }} (${{ env.CONTRIBUTOR_ID }}) as CLA signee
-        body: Xref ${{ github.event.html_url }}
+        body: |
+          Xref ${{ github.event.pull_request.user.html_url || github.event.issue.user.html_url }}
 
     # if unsigned, create sticky comment
     - name: Create comment regarding missing CLA signature
@@ -135,20 +136,17 @@ runs:
         number: ${{ github.event.number || github.event.issue.number }}
         # GitHub flavored markdown reinvents how paragraphs work, adjoined lines of text are not
         # concatenated so instead we rely on YAML multi-line + extra newlines
-        message: >-
+        message: |
           [cla]: https://conda.io/en/latest/contributing.html#conda-contributor-license-agreement
 
-
           > [!NOTE]
           > You may have previously signed the conda CLA. That signature is still valid
           > for any prior contributions however conda is now a NumFOCUS project and hence
           > requires new CLAs to be signed for any new contributions.
 
-
           We require contributors to sign our [Contributor License Agreement][cla] and we don't
           have one on file for @${{ env.CONTRIBUTOR_LOGIN }} (${{ env.CONTRIBUTOR_ID }}).
 
-
           In order for us to review and merge your code, please e-sign the
           [Contributor License Agreement PDF][cla]. We then need to manually verify your
           signature, merge the PR (${{ steps.pull.outputs.pull-request-url }}), and ping the bot