Skip to content

OSAC-3364: Remove Jira references from osac repo config content - #149

Merged
eliorerz merged 1 commit into
osac-project:mainfrom
eliorerz:OSAC-1732-repo-config-cleanup
Jul 29, 2026
Merged

OSAC-3364: Remove Jira references from osac repo config content#149
eliorerz merged 1 commit into
osac-project:mainfrom
eliorerz:OSAC-1732-repo-config-cleanup

Conversation

@eliorerz

Copy link
Copy Markdown
Contributor

Summary

Small follow-up to #148 — that PR's description field and code comments referenced a Jira ticket number directly in the repo config content, which shouldn't be there (ticket references belong in commit messages/Jira, not baked into a repo's own description or comments).

  • description field: drops the (OSAC-1732) parenthetical
  • Two code comments: drop the OSAC-1734/OSAC-1732 references, keep the actual explanation of why each setting is what it is

Test plan

  • tofu fmt -check clean
  • tofu validate passes

Ticket numbers belong in commit messages and Jira, not in a repo's
own description field or code comments -- those should read fine on
their own without cross-referencing an internal tracker.
@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 8 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: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 024238b5-1a69-40f3-a5a5-cd205afc04b1

📥 Commits

Reviewing files that changed from the base of the PR and between 615f4b4 and 557f773.

📒 Files selected for processing (1)
  • repositories.tf

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.

@eliorerz
eliorerz merged commit 346500b into osac-project:main Jul 29, 2026
2 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.

1 participant