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 default user for the user #546

Merged
merged 1 commit into from
Jan 20, 2025
Merged

Fix default user for the user #546

merged 1 commit into from
Jan 20, 2025

Conversation

jakubno
Copy link
Member

@jakubno jakubno commented Jan 20, 2025

Description

The column was moved from Team to UserTeam, because one team can be the default for a specific user, but not to all of them. This is addressing the logic in dashboard

@jakubno jakubno requested a review from mishushakov as a code owner January 20, 2025 23:02
Copy link

changeset-bot bot commented Jan 20, 2025

⚠️ No Changeset found

Latest commit: 1c1a681

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@jakubno jakubno merged commit 61cc00a into main Jan 20, 2025
2 checks passed
@jakubno jakubno deleted the fix-is-default branch January 20, 2025 23:15
@mishushakov
Copy link
Member

@ben-fornefeld can you check if this affects Fragments also?

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