Skip to content

MGMT-21375: Show link to cluster details on cluster install action#3110

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
rawagner:chatbot_details_link
Aug 13, 2025
Merged

MGMT-21375: Show link to cluster details on cluster install action#3110
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
rawagner:chatbot_details_link

Conversation

@rawagner
Copy link
Copy Markdown
Member

@rawagner rawagner commented Aug 12, 2025

Summary by CodeRabbit

  • New Features

    • Chatbot messages include an “Open cluster details” action that navigates to a cluster’s details page.
    • Message actions now support either download or cluster navigation; only the relevant button is shown.
  • Style

    • Action buttons clarified with distinct icons and titles for “Download” and “Open cluster details”.
  • Chores

    • Chat UI now accepts and forwards a cluster-navigation handler to enable in-chat navigation.

@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Aug 12, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 12, 2025
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Aug 12, 2025

Walkthrough

Adds an openClusterDetails callback threaded from the app into ChatBot → ChatBotWindow → BotMessage, introduces a MsgAction type carrying optional url or clusterId and maps install/create cluster tool responses to clusterId actions, and removes credentials:'include' from the streaming fetch.

Changes

Cohort / File(s) Summary
App integration (navigate to cluster details)
apps/assisted-ui/src/components/Chatbot.tsx
Adds React/router imports, initializes navigate() and passes an openClusterDetails(id) callback to the AIChatBot to route to /assisted-installer/clusters/{id}.
Chatbot component wiring
libs/chatbot/lib/components/ChatBot/ChatBot.tsx, .../ChatBotWindow.tsx
Extends public props to include openClusterDetails and forwards it from ChatBotChatBotWindowBotMessage.
Bot message actions / UI
libs/chatbot/lib/components/ChatBot/BotMessage.tsx
Adds openClusterDetails to BotMessageProps; renders either a Download button when url exists or an ExternalLinkAltIcon button that calls openClusterDetails(clusterId) when clusterId exists.
Helpers / action model
libs/chatbot/lib/components/ChatBot/helpers.ts
Introduces MsgAction = { title: string; url?: string; clusterId?: string }, updates MsgProps.actions and getToolAction types, and adds install_cluster and create_cluster mappings returning clusterId actions.
Streaming hook
libs/chatbot/lib/hooks/use-message.ts
Removes credentials: 'include' from the /v1/streaming_query fetch options; other fetch behavior unchanged.

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant App (Chat UI)
  participant ChatBot
  participant ChatBotWindow
  participant BotMessage
  participant Router

  User->>App: Open chat / interact
  App->>ChatBot: render with props { onApiCall, username, openClusterDetails }
  ChatBot->>ChatBotWindow: forward props
  ChatBotWindow->>BotMessage: render message with actions (url? / clusterId?)
  User->>BotMessage: Click "Open cluster details page"
  BotMessage->>Router: openClusterDetails(clusterId)
  Router-->>User: Navigate to /assisted-installer/clusters/{id}
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested labels

lgtm

Suggested reviewers

  • ElayAharoni
  • celdrake
  • ammont82

Poem

I twitch my ears at links and trails,
A hop to clusters, no more details fails.
One button saves, the other takes flight,
From chat to cluster in a single sight—
A rabbit routes with glee tonight. 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Aug 12, 2025
@rawagner rawagner force-pushed the chatbot_details_link branch from a45f9c0 to edae9a7 Compare August 13, 2025 06:49
@rawagner rawagner changed the title Chatbot details link MGMT-21375: Show link to cluster details on cluster install action Aug 13, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 13, 2025

@rawagner: This pull request references MGMT-21375 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot removed the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 13, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 13, 2025
@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 13, 2025
@rawagner rawagner marked this pull request as ready for review August 13, 2025 06:50
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 13, 2025
@openshift-ci openshift-ci bot requested review from ammont82 and celdrake August 13, 2025 06:50
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 13, 2025

@rawagner: This pull request references MGMT-21375 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

  • New Features
  • Chatbot messages now include an “Open cluster details” action that navigates directly to a cluster’s details page.
  • Message actions support both downloads and cluster navigation, showing buttons only when relevant.
  • Style
  • Updated chatbot action rendering to clearly separate “Download” and “Open cluster details” buttons with appropriate icons and titles.

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🔭 Outside diff range comments (2)
libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx (1)

26-39: Make openClusterDetails optional with a no-op default to preserve API compatibility

This avoids a breaking change for consumers that don’t need cluster navigation.

 export type ChatBotWindowProps = {
   error?: string;
   resetError: VoidFunction;
   conversationId: string | undefined;
   messages: MsgProps[];
   onApiCall: typeof fetch;
   username: string;
   onClose: () => void;
   sentMessage: (msg: string) => Promise<unknown>;
   startNewConversation: VoidFunction;
   isStreaming: boolean;
   announcement: string | undefined;
-  openClusterDetails: (clusterId: string) => void;
+  openClusterDetails?: (clusterId: string) => void;
 };

And in the component parameters:

-  openClusterDetails,
+  openClusterDetails = () => undefined,
libs/chatbot/lib/components/ChatBot/BotMessage.tsx (1)

115-147: Prevent rendering a stray “0” when actions is an empty array

Using && with a numeric length can render 0. Coerce to boolean.

-              {!isLoading && message.actions?.length && (
+              {!isLoading && !!message.actions?.length && (
                 <Stack hasGutter>
                   {message.actions.map(({ title, url, clusterId }, idx) => (
                     <StackItem key={idx}>
                       {url && (
                         <Button
                           onClick={() => {
                             try {
                               saveAs(url);
                             } catch (error) {
                               // eslint-disable-next-line
                               console.error('Download failed: ', error);
                             }
                           }}
                           variant="secondary"
                           icon={<DownloadIcon />}
+                          aria-label={title}
                         >
                           {title}
                         </Button>
                       )}
                       {clusterId && (
                         <Button
                           onClick={() => openClusterDetails(clusterId)}
                           variant="secondary"
                           icon={<ExternalLinkAltIcon />}
+                          aria-label={title}
                         >
                           {title}
                         </Button>
                       )}
                     </StackItem>
                   ))}
                 </Stack>
               )}
🧹 Nitpick comments (4)
libs/chatbot/lib/components/ChatBot/helpers.ts (1)

53-55: Internationalize user-facing strings

Wrap labels in your i18n util so they can be localized.

Example:

  • 'Download ISO'
  • Download ${args?.file_name || 'credentials'}
  • 'Open cluster details page'

Also applies to: 71-73, 79-81

apps/assisted-ui/src/components/Chatbot.tsx (1)

51-60: Stabilize onApiCall with useCallback

Prevents unnecessary re-renders of children relying on referential equality. No behavior change.

-  const onApiCall: ChatBotWindowProps['onApiCall'] = async (input, init) => {
+  const onApiCall: ChatBotWindowProps['onApiCall'] = React.useCallback(async (input, init) => {
     const token = await getOcmToken();
     return fetch(`/chatbot${input.toString()}`, {
       ...(init || {}),
       headers: {
         ...(init?.headers || {}),
         Authorization: `Bearer ${token}`,
       },
     });
-  };
+  }, []);
libs/chatbot/lib/components/ChatBot/BotMessage.tsx (2)

7-7: Standardize icon imports to avoid bundle duplication

Other files import icons from '/dist/js/icons/...'. Align to one style to prevent multiple icon builds.

-import { DownloadIcon, ExternalLinkAltIcon } from '@patternfly-6/react-icons';
+import { DownloadIcon } from '@patternfly-6/react-icons/dist/js/icons/download-icon';
+import { ExternalLinkAltIcon } from '@patternfly-6/react-icons/dist/js/icons/external-link-alt-icon';

117-145: Consider deterministic keys and mutually exclusive actions

  • Use a stable key (e.g., title) instead of the array index if possible.
  • If an item ever contains both url and clusterId, you’ll render two buttons; confirm this is intended. If not, prefer else-if.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3c82686 and edae9a7.

📒 Files selected for processing (6)
  • apps/assisted-ui/src/components/Chatbot.tsx (3 hunks)
  • libs/chatbot/lib/components/ChatBot/BotMessage.tsx (4 hunks)
  • libs/chatbot/lib/components/ChatBot/ChatBot.tsx (2 hunks)
  • libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx (3 hunks)
  • libs/chatbot/lib/components/ChatBot/helpers.ts (3 hunks)
  • libs/chatbot/lib/hooks/use-message.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • libs/chatbot/lib/hooks/use-message.ts
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-18T12:35:50.945Z
Learnt from: celdrake
PR: openshift-assisted/assisted-installer-ui#3051
File: libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx:196-222
Timestamp: 2025-07-18T12:35:50.945Z
Learning: In the assisted-installer-ui chatbot feedback implementation, the onFeedbackSubmit callback requires access to the messages array to retrieve both the bot response content and the associated user question for the API call, making it necessary to include messages in the useCallback dependency array rather than passing message content as props to avoid duplicating potentially long message data.

Applied to files:

  • libs/chatbot/lib/components/ChatBot/ChatBot.tsx
🧬 Code Graph Analysis (1)
libs/chatbot/lib/components/ChatBot/ChatBot.tsx (2)
libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx (1)
  • ChatBotWindowProps (26-39)
libs/chatbot/lib/index.ts (1)
  • ChatBotWindowProps (2-2)
🔇 Additional comments (5)
apps/assisted-ui/src/components/Chatbot.tsx (1)

2-2: Router compat import LGTM

useNavigate from react-router-dom-v5-compat is appropriate for v5-compatible navigation.

libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx (1)

150-151: Prop plumbing to BotMessage looks correct

Prop is forwarded to BotMessage where it’s used. Once the prop is made optional, the default will keep this safe.

libs/chatbot/lib/components/ChatBot/ChatBot.tsx (2)

25-33: Forward optional openClusterDetails safely

If left undefined by consumers, ChatBotWindow will use its no-op default.


5-5: Import path change for useMessages is fine

No functional impact. Just ensure tree-shaking doesn’t duplicate hook code.

libs/chatbot/lib/components/ChatBot/BotMessage.tsx (1)

45-67: Feedback submit hook dependencies look good

Including message and userMsg in the dependency array matches prior guidance to avoid stale closures.

@rawagner rawagner force-pushed the chatbot_details_link branch from edae9a7 to 801a447 Compare August 13, 2025 07:08
@rawagner
Copy link
Copy Markdown
Member Author

/cherry-pick releases/v0.1-chatbot

@openshift-cherrypick-robot
Copy link
Copy Markdown
Contributor

@rawagner: once the present PR merges, I will cherry-pick it on top of releases/v0.1-chatbot in a new PR and assign it to you.

Details

In response to this:

/cherry-pick releases/v0.1-chatbot

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.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 13, 2025

@rawagner: This pull request references MGMT-21375 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

  • New Features

  • Chatbot messages now include an “Open cluster details” action that navigates directly to a cluster’s details page.

  • Message actions support both downloads and cluster navigation, showing only the relevant button for each action.

  • Style

  • Action buttons clarified: distinct “Download” and “Open cluster details” buttons with appropriate icons and titles.

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 openshift-eng/jira-lifecycle-plugin repository.

@rawagner rawagner force-pushed the chatbot_details_link branch from 801a447 to e8eec16 Compare August 13, 2025 07:52
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Aug 13, 2025

@rawagner: This pull request references MGMT-21375 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

  • New Features

  • Chatbot messages include an “Open cluster details” action that navigates to a cluster’s details page.

  • Message actions now support either download or cluster navigation; only the relevant button is shown.

  • Style

  • Action buttons clarified with distinct icons and titles for “Download” and “Open cluster details”.

  • Chores

  • Chat UI now accepts and forwards a cluster-navigation handler to enable in-chat navigation.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 13, 2025
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Aug 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ammont82, rawagner

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

The pull request process is described 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

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

♻️ Duplicate comments (3)
libs/chatbot/lib/components/ChatBot/helpers.ts (2)

4-4: Export MsgAction type to avoid leaking private type

The MsgAction type is used in the exported MsgProps interface but is not exported itself, which can cause issues for consumers trying to type actions without relying on internal implementation details.


76-83: Fix switch statement fall-through

The install_cluster case is missing a break or return statement, causing it to fall through to the create_cluster case when the condition isn't met.

libs/chatbot/lib/components/ChatBot/ChatBot.tsx (1)

9-9: Make openClusterDetails optional to avoid breaking change

The current implementation makes openClusterDetails a required prop, which creates a breaking change for existing consumers of the ChatBot component.

🧹 Nitpick comments (1)
libs/chatbot/lib/components/ChatBot/BotMessage.tsx (1)

117-143: Action rendering logic looks good with minor improvement opportunity

The conditional rendering of buttons based on url and clusterId is well implemented. Both action types are properly handled with appropriate icons and error handling for downloads.

Consider adding a fallback for actions that have neither url nor clusterId to help with debugging:

                  {message.actions.map(({ title, url, clusterId }, idx) => (
                    <StackItem key={idx}>
                      {url && (
                        <Button
                          onClick={() => {
                            try {
                              saveAs(url);
                            } catch (error) {
                              // eslint-disable-next-line
                              console.error('Download failed: ', error);
                            }
                          }}
                          variant="secondary"
                          icon={<DownloadIcon />}
                        >
                          {title}
                        </Button>
                      )}
                      {clusterId && (
                        <Button
                          onClick={() => openClusterDetails(clusterId)}
                          variant="secondary"
                          icon={<ExternalLinkAltIcon />}
                        >
                          {title}
                        </Button>
                      )}
+                     {!url && !clusterId && (
+                       console.warn('Action has no url or clusterId:', { title, url, clusterId })
+                     )}
                    </StackItem>
                  ))}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 801a447 and e8eec16.

📒 Files selected for processing (6)
  • apps/assisted-ui/src/components/Chatbot.tsx (3 hunks)
  • libs/chatbot/lib/components/ChatBot/BotMessage.tsx (4 hunks)
  • libs/chatbot/lib/components/ChatBot/ChatBot.tsx (2 hunks)
  • libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx (3 hunks)
  • libs/chatbot/lib/components/ChatBot/helpers.ts (3 hunks)
  • libs/chatbot/lib/hooks/use-message.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • libs/chatbot/lib/hooks/use-message.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-18T12:35:50.945Z
Learnt from: celdrake
PR: openshift-assisted/assisted-installer-ui#3051
File: libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx:196-222
Timestamp: 2025-07-18T12:35:50.945Z
Learning: In the assisted-installer-ui chatbot feedback implementation, the onFeedbackSubmit callback requires access to the messages array to retrieve both the bot response content and the associated user question for the API call, making it necessary to include messages in the useCallback dependency array rather than passing message content as props to avoid duplicating potentially long message data.

Applied to files:

  • libs/chatbot/lib/components/ChatBot/ChatBot.tsx
🧬 Code Graph Analysis (2)
libs/chatbot/lib/components/ChatBot/ChatBot.tsx (1)
libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx (1)
  • ChatBotWindowProps (26-39)
apps/assisted-ui/src/components/Chatbot.tsx (1)
libs/chatbot/lib/components/ChatBot/ChatBotWindow.tsx (1)
  • ChatBotWindowProps (26-39)
🪛 Biome (2.1.2)
libs/chatbot/lib/components/ChatBot/helpers.ts

[error] 76-83: This case is falling through to the next case.

Add a break or return statement to the end of this case to prevent fallthrough.

(lint/suspicious/noFallthroughSwitchClause)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: translation-files
  • GitHub Check: tests
  • GitHub Check: unit-tests
  • GitHub Check: lint
  • GitHub Check: circular-deps
  • GitHub Check: format
🔇 Additional comments (3)
libs/chatbot/lib/components/ChatBot/ChatBot.tsx (1)

32-32: LGTM! Props forwarding implemented correctly

The openClusterDetails prop is correctly forwarded to the ChatBotWindow component, maintaining the callback chain for cluster navigation functionality.

apps/assisted-ui/src/components/Chatbot.tsx (1)

52-61: LGTM! Token handling preserved correctly

The onApiCall callback correctly maintains the existing token retrieval and authorization header logic while being properly memoized to avoid unnecessary re-renders.

libs/chatbot/lib/components/ChatBot/BotMessage.tsx (1)

28-28: LGTM! Proper callback integration

The openClusterDetails prop is correctly typed and integrated into the component props, enabling cluster navigation functionality from chat messages.

@openshift-merge-bot openshift-merge-bot bot merged commit 86daafa into openshift-assisted:master Aug 13, 2025
11 checks passed
@openshift-cherrypick-robot
Copy link
Copy Markdown
Contributor

@rawagner: new pull request created: #3113

Details

In response to this:

/cherry-pick releases/v0.1-chatbot

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants