Skip to content

Conversation

@adity1raut
Copy link
Contributor

Description

Related Issue

Fixes #2080

Changes Made

  • Updated ...
  • Refactored ...
  • Fixed ...
  • Added tests for ...

Checklist

Please ensure the following before submitting your PR:

  • I have reviewed the project's contribution guidelines.
  • I have written unit tests for the changes (if applicable).
  • I have updated the documentation (if applicable).
  • I have tested the changes locally and ensured they work as expected.
  • My code follows the project's coding standards.

Screenshots or Logs (if applicable)

Additional Notes

Signed-off-by: adity1raut <[email protected]>
@kubestellar-prow kubestellar-prow bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 8, 2025
@kubestellar-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mavrick-1 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@github-actions github-actions bot added the backend Issues or PRs related to the low-level API machinery for KubeStellar label Nov 8, 2025
@kubestellar-prow
Copy link

Hi @adity1raut. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubestellar-prow kubestellar-prow bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 8, 2025
@adity1raut
Copy link
Contributor Author

Also, which changes do you want @alokdangre

@alokdangre
Copy link
Contributor

@adity1raut for solving this first we need to solve other issues of the user management which i have made and then after good working of the user management, we can give specific errors to user
so if possible try to fix other user management issues first

@SakshamDutt
Copy link
Contributor

@alokdangre What's the status of this PR? Do we need it?

@clubanderson
Copy link
Contributor

can we get a better title for this?

@btwshivam btwshivam closed this Dec 6, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in KubeStellar UI Project Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend Issues or PRs related to the low-level API machinery for KubeStellar do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[Bug]: Not proper error message when different user comes

5 participants