The branch, master has been updated
       via  883162d5b4107dfe8c8a3efef3dd798bc4cf7a63 (commit)
      from  b2910ec92ef0f12f2cee56be331f8ae234ead4a4 (commit)


- Log -----------------------------------------------------------------
commit 883162d5b4107dfe8c8a3efef3dd798bc4cf7a63
Author:     Timo Rothenpieler <[email protected]>
AuthorDate: Mon Sep 1 03:02:49 2025 +0200
Commit:     Timo Rothenpieler <[email protected]>
CommitDate: Mon Sep 1 03:02:51 2025 +0200

    forgejo/workflows: make autolabel workflow always use token from secrets
    
    Using the built-in token seems to only partially work.
    And in the latest Forgejo release the issue forcing the use of the
    built-in token was fixed with:
    
    https://codeberg.org/forgejo/forgejo/pulls/9025

diff --git a/.forgejo/workflows/autolabel.yml b/.forgejo/workflows/autolabel.yml
index 85afcdad03..cb4dac67aa 100644
--- a/.forgejo/workflows/autolabel.yml
+++ b/.forgejo/workflows/autolabel.yml
@@ -18,11 +18,11 @@ jobs:
         if: ${{ forge.event_name == 'pull_request_target' }}
         with:
           configuration-path: .forgejo/labeler/labeler.yml
-          repo-token: ${{ forge.event_name == 'pull_request_target' && 
secrets.AUTOLABELER_TOKEN || forge.token }}
+          repo-token: ${{ secrets.AUTOLABELER_TOKEN }}
       - name: Label by title-match
         uses: https://github.com/actions/github-script@v7
         with:
           script: |
             const script = require('.forgejo/labeler/labeler.js')
             await script({github, context})
-          github-token: ${{ forge.event_name == 'pull_request_target' && 
secrets.AUTOLABELER_TOKEN || forge.token }}
+          github-token: ${{ secrets.AUTOLABELER_TOKEN }}

-----------------------------------------------------------------------

Summary of changes:
 .forgejo/workflows/autolabel.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 

_______________________________________________
ffmpeg-cvslog mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to