Update TagBot config #255
Merged
Update TagBot config #255
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think this should be uncontroversial and only affects currently broken GH actions, so I'll merge and check whether it improves things. |
|
I wanted to check the settings of the repo but I don't have access: are the documenter key and secret correctly set up? Otherwise TagBot won't succeed in triggering docs build. |
|
@devmotion should we push a Documenter tag to see if your setup worked? |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@gdalle #253 didn't fix the stable docs build. https://github.com/JuliaDiff/ReverseDiff.jl/actions shows that the TagBot action executed successfully but did not trigger a docs build. I assume the remaining issue might be an outdated TagBot config. In this PR I copied the recommended TagBot config.