feat(ci): Automatically close the previous "Repository Health Check Failed" issue before opening the new one #27165
Conversation
2b6e8d5 to
71cb3aa
Compare
9e5c9a1 to
2f6e9ea
Compare
- Test termux#27165
- Test termux#27165
|
I ran a test in my fork repository on account @owokitty, which is visible in the GitHub links above, and it does successfully detect my placeholder test "Repository Health Check Failed" issue in my fork, however, unfortunately I wasn't able to complete a full test of detecting and also closing the issue, because when it got to the part of the script where I'm assuming that this error occurs because my fork doesn't have access to the real @termuxbot2 and the real repository to test with, so it doesn't have the GitHub permission to close its own issues like that because my fork repository isn't the same as the real repository. I don't know if there's any way to test whether the same error would occur when attempting to use At the very least, my test has confirmed (I think) that the correct issue gets detected by the |
2f6e9ea to
2848402
Compare
- Test termux#27165
2848402 to
1a12af3
Compare
| ./scripts/check-repository-health.js "${{ steps.generate-apt-packages-list.outputs.OUTPUT_DIR }}" | tee repository-health.txt | ||
| - name: Create issue if health check fails | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.TERMUXBOT2_TOKEN }} |
There was a problem hiding this comment.
We are not using github runner's github token. So setting the permissions above makes no change at all. @Grimler91 does have control of the @termuxbot2, so you'll have to ask him about whether the user does have permissions for closing issues.
There was a problem hiding this comment.
Thanks for checking, I wasn't sure what the correct way to set the permissions was. I'll wait for Grimler to review this so that we know whether closing issues automatically is allowed (I don't think there has ever been a workflow that automatically closes issues here before).
There was a problem hiding this comment.
termuxbot2 has write access to termux-packages, which includes "can manage issues and pull requests", and its token includes public_repo scope, so it should be able to close issues
…ailed" issue before opening the new one
1a12af3 to
ff493ab
Compare
No description provided.