chore(financial-aid): update codeowners

[jonnigs]

What

Update financial aid template codeowners to Norda

Why

Kolibri isn't maintaining it anymore

Summary by CodeRabbit

• Chores
  • Updated code ownership for financial aid templates and modules
  • Transferred responsibility from @island-is/kolibri-robin-hood to @island-is/norda

[coderabbitai]

Walkthrough

The pull request involves updating the .github/CODEOWNERS file to reassign ownership of specific project paths related to financial aid templates and modules. The ownership for two paths previously assigned to @island-is/kolibri-robin-hood has been transferred to @island-is/norda. This change reflects a shift in team responsibilities for these specific project components, with the overall file structure remaining consistent.

Changes

File	Change Summary
.github/CODEOWNERS	Transferred ownership of financial aid template and module paths from @island-is/kolibri-robin-hood to @island-is/norda

Possibly related PRs

• chore(system-e2e): Move system test ownership to relevant teams #16479: Modifies .github/CODEOWNERS file, updating ownership assignments
• chore(University-Gateway): Change ownership of UG queries #16634: Updates .github/CODEOWNERS file, changing ownership for specific files
• chore(codeowners): modify ownership of health directorate clients #16904: Modifies .github/CODEOWNERS file, reallocating ownership responsibilities

Suggested labels

automerge

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 068bfc6 and db498ad.

📒 Files selected for processing (1)

• .github/CODEOWNERS (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: prepare

🔇 Additional comments (1)

.github/CODEOWNERS (1)

247-248: LGTM! Ownership transfer looks correct.

The ownership transfer from @island-is/kolibri-robin-hood to @island-is/norda for the financial aid template paths aligns with the PR objectives.

Run the following script to verify the team name exists and check for any inconsistencies in path patterns:

✅ Verification successful

Ownership transfer verified successfully

The team name and path patterns are consistent with existing entries in the CODEOWNERS file. The @island-is/norda team already owns several other templates, and the financial aid template paths follow the same established patterns.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify team name exists and path patterns are consistent

# Test 1: Check if the team name exists in other parts of the file
echo "Verifying team name exists:"
rg "@island-is/norda(?!\w)" .github/CODEOWNERS

# Test 2: Check for any inconsistencies in template path patterns
echo -e "\nVerifying path patterns are consistent:"
rg "^/libs/application/templates/.*?/\s+@" .github/CODEOWNERS
rg "^/libs/application/template-api-modules/src/lib/modules/templates/.*?\s+@" .github/CODEOWNERS

Length of output: 12691

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[brynjarorng]

LGTM

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 35.60%. Comparing base (5844fd2) to head (2f83839).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #17542   +/-   ##
=======================================
  Coverage   35.60%   35.60%           
=======================================
  Files        7020     7020           
  Lines      150478   150478           
  Branches    42988    42988           
=======================================
  Hits        53583    53583           
  Misses      96895    96895           

Flag	Coverage Δ
api	3.33% <ø> (ø)
application-system-api	38.69% <ø> (+<0.01%)	⬆️
application-template-api-modules	27.58% <ø> (+<0.01%)	⬆️
application-templates-marriage-conditions	14.80% <ø> (ø)
application-templates-new-primary-school	21.02% <ø> (ø)
application-ui-shell	22.01% <ø> (ø)
judicial-system-api	20.11% <ø> (ø)
judicial-system-backend	55.81% <ø> (ø)
judicial-system-formatters	78.54% <ø> (ø)
judicial-system-web	27.98% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5844fd2...2f83839. Read the comment docs.

[datadog-island-is]

Datadog Report

All test runs 81da754 🔗

✅ 9 Total Test Services: 0 Failed, 9 Passed
➡️ Test Sessions change in coverage: 15 no change

Test Services

Service Name	Failed	Known Flaky	New Flaky	Passed	Skipped	Total Time	Code Coverage Change	Test Service View
api	0	0	0	4	0	2.4s	1 no change	Link
application-system-api	0	0	0	46	0	2m 24.66s	1 no change	Link
application-template-api-modules	0	0	0	118	0	2m 5.7s	1 no change	Link
application-ui-shell	0	0	0	74	0	31.14s	1 no change	Link
judicial-system-api	0	0	0	61	0	5.37s	1 no change	Link
judicial-system-backend	0	0	0	21356	0	18m 56.16s	1 no change	Link
judicial-system-formatters	0	0	0	40	0	4.85s	1 no change	Link
judicial-system-web	0	0	0	333	0	57.62s	1 no change	Link
judicial-system-xrd-api	0	0	0	6	0	4.72s	1 no change	Link