-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github release out of date #137
Comments
We've been trying to fix tagbot, but at this point I have no idea how to do that. It probably requires intervention from people who have more permissions than I do. |
I'm not expert, but I do notice that the current TagBot.yml is missing a ssh key. (There is a name: TagBot
on:
issue_comment:
types:
- created
workflow_dispatch:
inputs:
lookback:
default: 3
permissions:
actions: read
checks: read
contents: write
deployments: read
issues: read
discussions: read
packages: read
pages: read
pull-requests: read
repository-projects: read
security-events: read
statuses: read
jobs:
TagBot:
if: github.event_name == 'workflow_dispatch' || github.actor == 'JuliaTagBot'
runs-on: ubuntu-latest
steps:
- uses: JuliaRegistries/TagBot@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
# Edit the following line to reflect the actual name of the GitHub Secret containing your private key
ssh: ${{ secrets.DOCUMENTER_KEY }}
# ssh: ${{ secrets.NAME_OF_MY_SSH_PRIVATE_KEY_SECRET }} So if this is added, and someone with privileges adds a corresponding secret key in the repo Settings, then maybe that will fix this.... |
@aviks ? |
bump |
@Moelf I now have as much privileges on this repo as @ExpandingMan. I do not think adding this key is necessary. I don't add this to any of my personal repos, and it seems to work. Here's and example from a couple of weeks ago: Tagbot Run, Workflow file. You'll notice the run succeeded, and the workflow file does not have any ssh key defined. It only uses the default There have been long term reports about Tagbot being flakey in the past few months: JuliaRegistries/TagBot#242 |
Also, it looks like the last Tagbot run succeeded, and |
Thanks for fixing. |
and documentation is not versioned, with breaking change this is un-usable for previous version
The text was updated successfully, but these errors were encountered: