Add repository name to recent releases

[aramattamara]

Replaced tag name with release name and release repository name for Recent Releases on Home and User Pages.

[coderabbitai]

Summary by CodeRabbit

• New Features
  • Release details now include repository names, offering enhanced contextual information about each release across the app.
• Style Updates
  • Updated the visual presentation of release items with a refreshed icon, reinforcing the focus on repository information.

Walkthrough

This pull request adds repository name fields across the application. On the backend, a new field and resolver are introduced in the ReleaseNode, with corresponding test updates. On the frontend, multiple GraphQL queries are extended to include the repositoryName field. UI components, type definitions, and end-to-end tests have been updated to support and display the repository name instead of previous tag-based identifiers.

Changes

File(s)	Change Summary
backend/apps/github/graphql/nodes/release.py backend/tests/apps/github/graphql/nodes/release_test.py	Added new field repository_name and resolver resolve_repository_name to ReleaseNode and updated tests to include this field in the expected meta configuration.
frontend/src/api/queries/homeQueries.ts frontend/src/api/queries/userQueries.ts frontend/src/api/queries/projectQueries.ts frontend/src/api/queries/repositoryQueries.ts	Added repositoryName field to various GraphQL queries (GET_MAIN_PAGE_DATA, GET_USER_DATA, GET_PROJECT_DATA, GET_REPOSITORY_DATA) so that each release returns its repository name.
frontend/src/pages/UserDetails.tsx frontend/src/types/project.ts frontend/src/components/RecentReleases.tsx	Updated frontend components and type definitions to pass and display repositoryName. In RecentReleases.tsx, changed the icon from faTag to faFileCode and replaced property access from tagName to repositoryName.
frontend/__tests__/e2e/data/mockHomeData.ts frontend/__tests__/e2e/pages/Home.spec.ts	Modified mock data and end-to-end tests to replace tagName with repositoryName, ensuring test expectations reflect the updated release information.

Suggested labels

backend-tests, frontend-tests

Suggested reviewers

• kasya
• aramattamara

---

📜 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 29ec667 and 6e5c7f8.

📒 Files selected for processing (11)

• backend/apps/github/graphql/nodes/release.py (2 hunks)
• backend/tests/apps/github/graphql/nodes/release_test.py (1 hunks)
• frontend/__tests__/e2e/data/mockHomeData.ts (1 hunks)
• frontend/__tests__/e2e/pages/Home.spec.ts (1 hunks)
• frontend/src/api/queries/homeQueries.ts (1 hunks)
• frontend/src/api/queries/projectQueries.ts (1 hunks)
• frontend/src/api/queries/repositoryQueries.ts (1 hunks)
• frontend/src/api/queries/userQueries.ts (1 hunks)
• frontend/src/components/RecentReleases.tsx (3 hunks)
• frontend/src/pages/UserDetails.tsx (1 hunks)
• frontend/src/types/project.ts (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (5)

• frontend/src/pages/UserDetails.tsx
• frontend/src/api/queries/userQueries.ts
• frontend/src/api/queries/homeQueries.ts
• frontend/src/types/project.ts
• backend/apps/github/graphql/nodes/release.py

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

• GitHub Check: Run frontend e2e tests
• GitHub Check: Run backend tests
• GitHub Check: Run frontend unit tests
• GitHub Check: CodeQL (python)
• GitHub Check: CodeQL (javascript-typescript)

🔇 Additional comments (9)

frontend/src/api/queries/projectQueries.ts (1)

35-35: LGTM: Added repositoryName field to expand release data.

The addition of the repositoryName field to the recentReleases section of the GraphQL query allows for displaying repository context alongside release information, which aligns perfectly with the PR objective to enhance release displays.

frontend/src/api/queries/repositoryQueries.ts (1)

35-35: LGTM: Consistently added repositoryName field to repository queries.

The addition of the repositoryName field maintains consistency with the changes made in other query files, ensuring all release-related data includes repository context.

frontend/__tests__/e2e/pages/Home.spec.ts (1)

67-67: LGTM: Updated test assertion to match new UI behavior.

The test has been appropriately updated to verify that the repository name ('nest-repository-1') is displayed instead of the tag name, validating the UI changes implemented in this PR.

backend/tests/apps/github/graphql/nodes/release_test.py (1)

27-27: LGTM: Added repository_name field to test assertion.

The expected fields set has been properly updated to include the new repository_name field, ensuring that the backend schema changes are properly tested.

frontend/src/components/RecentReleases.tsx (3)

1-1: Icon change appropriately reflects content type

The change from faTag to faFileCode better represents the repository context that's now being displayed.

---

20-20: Consistent icon update in card header

Good job consistently updating the icon in the SecondaryCard component to match the new data representation.

---

56-57: Repository name display aligns with PR objective

Replacing the tag name with repository name provides better context for users viewing releases. The icon update to faFileCode matches the content type being displayed.

frontend/__tests__/e2e/data/mockHomeData.ts (2)

149-149: Mock data properly updated for testing

The test data has been correctly updated to reflect the schema changes, replacing tagName with repositoryName.

---

157-157: Appropriate repository naming convention

Good choice of mock repository names that follow a sensible convention with organization prefix ('nest' and 'owasp').

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[arkid15r]

LGTM 👍