Skip to content
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

Bug 1926095 - Add how-to with tips on investigating data anomalies #2979

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

travis79
Copy link
Member

No description provided.

@travis79 travis79 requested a review from a team as a code owner October 21, 2024 19:39
@travis79 travis79 requested review from badboy and removed request for a team October 21, 2024 19:39
Copy link
Member

@badboy badboy left a comment

Choose a reason for hiding this comment

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

some nits.

Would it maybe make sense which columns to query? A lot of them are standardized, so we could list them.

@travis79 travis79 requested a review from badboy October 24, 2024 12:04
@travis79
Copy link
Member Author

some nits.

Would it maybe make sense which columns to query? A lot of them are standardized, so we could list them.

Well, I suppose I could add that info... let me do that before you review again

@travis79
Copy link
Member Author

Okay, I added column names where appropriate and other links. Ready for another look @badboy

@travis79 travis79 enabled auto-merge (rebase) October 24, 2024 12:22
@travis79 travis79 merged commit 425ab80 into main Oct 24, 2024
28 of 30 checks passed
@travis79 travis79 deleted the Bug1926095 branch October 24, 2024 12:33
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.

2 participants