Skip to content

fix default nodes #1709

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

Merged
merged 1 commit into from
Oct 2, 2024
Merged

fix default nodes #1709

merged 1 commit into from
Oct 2, 2024

Conversation

BillWagner
Copy link
Member

I also moved the default node down one so it's easier to find. the value for the freshness node didn't change.

I also moved the default node down one so it's easier to find. the value for the freshness node didn't change.
@BillWagner BillWagner enabled auto-merge October 1, 2024 20:17
@dotnet-policy-service dotnet-policy-service bot added the okr-freshness OKR: Freshness of content label Oct 1, 2024
@BillWagner BillWagner merged commit f4f6b9e into dotnet:main Oct 2, 2024
7 checks passed
@BillWagner BillWagner deleted the fix-selenium-nodes branch October 2, 2024 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
okr-freshness OKR: Freshness of content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants