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

fix: use named diagnostic collection #721

Merged
merged 1 commit into from
Aug 31, 2022
Merged

Conversation

timonwong
Copy link
Member

@timonwong timonwong commented Aug 31, 2022

Creating named diagnostic collection correctly set the "owner" field.

Closes #666

Creating named diagnostic collection correctly set the "owner" field.

Related: #666

Signed-off-by: Timon Wong <timon86.wang@gmail.com>
@felipecrs felipecrs merged commit 562186d into master Aug 31, 2022
@felipecrs felipecrs deleted the create-named-diagcollection branch August 31, 2022 12:09
timonwong pushed a commit that referenced this pull request Aug 31, 2022
## [0.21.4](v0.21.3...v0.21.4) (2022-08-31)

### Bug Fixes

* use named diagnostic collection ([#721](#721)) ([562186d](562186d)), closes [#666](#666)
@github-actions
Copy link

🎉 This PR is included in version 0.21.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Source" in problem panel can be misreported as " "_generated_diagnostic_collection_name_#0"
2 participants