Run docs CI on Augur code changes#2002
Closed
victorlin wants to merge 1 commit into
Closed
Conversation
As noted in the commit message of "[export] fix incorrect type def" (9d178e5), the invalid type definition introduced in "[minor] refactor config transfer functions for export" (5981840) did not surface the failure until another PR touched docs-related files. This will result in unnecessary runs for code changes that don't touch docstrings, but that's fine and was already the case before splitting docs CI into its own workflow.
joverlee521
reviewed
May 20, 2026
Member
|
I've come to accept that I'll never remember which language uses |
7 tasks
3 tasks
joverlee521
added a commit
to nextstrain/cli
that referenced
this pull request
May 20, 2026
Paths were initially added to reduce noise from docs-ci due to linkcheck. We can now run docs-ci on every push/PR since we only include linkcheck on scheduled runs. This ensures that we capture doc changes that come from the source code similar to <nextstrain/augur#2002>
joverlee521
added a commit
to nextstrain/auspice
that referenced
this pull request
May 20, 2026
Paths were initially added to reduce noise from docs-ci due to linkcheck. We can now run docs-ci on every push/PR since we only include linkcheck on scheduled runs. Based on discussion in <nextstrain/augur#2002 (comment)>
joverlee521
added a commit
to nextstrain/ncov
that referenced
this pull request
May 20, 2026
Paths were initially added to reduce noise from docs-ci due to linkcheck. We can now run docs-ci on every push/PR since we only include linkcheck on scheduled runs. Based on discussion in <nextstrain/augur#2002 (comment)>
4 tasks
Contributor
|
Closing in favor of #2004 |
5 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description of proposed changes
As noted in the commit message of "[export] fix incorrect type def" (9d178e5), the invalid type definition introduced in "[minor] refactor config transfer functions for export" (5981840) did not surface the failure until another PR touched docs-related files.
This will result in unnecessary runs for code changes that don't touch docstrings, but that's fine and was already the case before splitting docs CI into its own workflow.
Related issue(s)
Follow-up to 9d178e5
Checklist
Check if you need to add a changelog messageCheck if you need to add testsCheck if you need to update docs