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: resource label errors for non-default organization resource change events #8008

Merged
merged 2 commits into from
Aug 30, 2024

Conversation

lzf575
Copy link
Contributor

@lzf575 lzf575 commented Aug 30, 2024

This PR is for:

  • Server

Affected branches

  • main
  • v6.5
  • v6.6.4

@lzf575 lzf575 requested a review from sharang August 30, 2024 03:34
@lzf575 lzf575 changed the title fix: resource change events of non-default organizations, resource ta… fix: resource change events of non-default organizations, resource tagging errors Aug 30, 2024
@lzf575 lzf575 force-pushed the feature-fix-resource-event branch from 68508ea to 661fc03 Compare August 30, 2024 03:36
@sharang
Copy link
Member

sharang commented Aug 30, 2024

Pr标题好像不太对,是个名词,不太清楚做了什么

@lzf575
Copy link
Contributor Author

lzf575 commented Aug 30, 2024

Pr标题好像不太对,是个名词,不太清楚做了什么

修复 非 defaulat 组织 的 资源变更事件, 资源标签错误

@lzf575 lzf575 marked this pull request as ready for review August 30, 2024 06:11
@lzf575 lzf575 changed the title fix: resource change events of non-default organizations, resource tagging errors fix: resource label errors for non-default organization resource change events Aug 30, 2024
@lzf575 lzf575 force-pushed the feature-fix-resource-event branch from 661fc03 to b03372d Compare August 30, 2024 06:14
@lzf575 lzf575 enabled auto-merge (rebase) August 30, 2024 06:26
@lzf575 lzf575 merged commit e265824 into main Aug 30, 2024
8 checks passed
@lzf575 lzf575 deleted the feature-fix-resource-event branch August 30, 2024 09:39
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