update tagbot and version#27
Conversation
|
Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue. |
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #27 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 4 4
Lines 86 86
=========================================
Hits 86 86 ☔ View full report in Codecov by Sentry. |
| 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 }} No newline at end of file |
There was a problem hiding this comment.
How does this work with DOCUMENTER_KEY?
There was a problem hiding this comment.
I think you just need to create the ssh key and the repo secret and make the with block look like this
with:
token: ${{ secrets.GITHUB_TOKEN }}
ssh: ${{ secrets.SSH_KEY }}
This is how atomsbase does it .
There was a problem hiding this comment.
@shivupa Can you do this since you did similar for cclib docs? I don't think I can access the SSH key.
berquist
left a comment
There was a problem hiding this comment.
We can fix the SSH key in a follow-up.
Updating tagbot configuration.
It should not work yet - for it to work one needs to deploy SSH keys as per here.
Doing that requires access I don't have. Therefore, will register this version manually.