Skip to content

User gets added with contributor#27

Merged
susrisha merged 1 commit into
developfrom
feature-task-3953
Jul 3, 2026
Merged

User gets added with contributor#27
susrisha merged 1 commit into
developfrom
feature-task-3953

Conversation

@susrisha

@susrisha susrisha commented Jul 3, 2026

Copy link
Copy Markdown
Collaborator

When a contributor is added to the TM project, if not available, the user needs to be provisioned in the workspaces db
This pull request updates the process for adding a new project role to support automatic user provisioning from TDEI if the user does not already exist in the system. The changes ensure that, when a user is missing, the system attempts to create the user using credentials and project group information, rather than immediately failing.

User provisioning improvements:

  • The add_role method in repository.py now accepts user_token and project_group_id parameters, and attempts to provision missing users from TDEI before raising an error if the user does not exist.
  • The add_project_role route in routes.py is updated to fetch the current user's credentials and the project's group ID, passing them to the repository method to support user provisioning.

@susrisha susrisha requested a review from MashB July 3, 2026 09:21
@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@susrisha, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5eeff7dc-2896-431f-8702-f9dbc6408bd3

📥 Commits

Reviewing files that changed from the base of the PR and between 4eefbdf and 7be1a53.

📒 Files selected for processing (2)
  • api/src/tasking/projects/repository.py
  • api/src/tasking/projects/routes.py

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

When a contributor is added to the TM project, if not available, the user needs to be provisioned in the workspaces db
@susrisha susrisha force-pushed the feature-task-3953 branch from a3770bc to 7be1a53 Compare July 3, 2026 09:22
@susrisha susrisha merged commit d19d3c5 into develop Jul 3, 2026
3 checks passed
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