Skip to content

Conversation

@BillWagner
Copy link
Member

One path through the code was missed in my tests. This fixes the path where all open issues with appropriate labels were examined.

One path through the code was missed in my tests. This fixes the path where all open issues with appropriate labels were examined.
@BillWagner
Copy link
Member Author

@gewarren After you approve this and we merge it, you should run Sequester on the dotnet-api-docs repo with a duration of -1. That will run and import all the loc issues that should have been imported over the weekend.

{
variables.importTriggerLabelText ?? throw new ArgumentException("The import trigger label can't be null"),
variables.importedLabelText ?? throw new ArgumentException("The imported label can't be null")
variables.importedLabelText ?? throw new ArgumentException("The imported label can't be null"),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Should we use the helper ArgumentException.ThrowIfNullOrEmpty instead? (example)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ordinarily, yet. But, this is in an expression context and that's a statement.

@BillWagner BillWagner merged commit 5fbaa50 into dotnet:main Dec 8, 2025
8 of 9 checks passed
@BillWagner BillWagner deleted the fix-loc-import branch December 8, 2025 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants