You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current auto-summarization feature in the highlight creation process sometimes produces summaries that are not optimal in the context of "pull requests", especially when the commit titles (acknowledging it looks up commit message for generating summaries) are not descriptive enough.
For example, sentences like "It also merges the beta branch into the refactor/typography-components-in-design-system branch." resulted from this.... see screenshot below for a summary that was generated for the stated pull request.
build: Add `@tailwindcss/typography` plugin, refactor typography components in design system
This PR adds the `@tailwindcss/typography` plugin to the build process and refactors the typography components in the design system. It also merges the `beta` branch into the `refactor/typography-components-in-design-system` branch.
Suggested solution
Prioritize the use of the pull request description for auto-summarization. I think Pull request descriptions typically provide a more comprehensive overview of the changes and goals of the pull request, which can lead to more informative and cleaner summaries.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
Contributing Docs
I agree to follow this project's Contribution Docs
The text was updated successfully, but these errors were encountered:
Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.
To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please reach out to us on Discord or follow up on the issue itself.
For full info on how to contribute, please check out our contributors guide.
Type of feature
🍕 Feature
Current behavior
The current auto-summarization feature in the highlight creation process sometimes produces summaries that are not optimal in the context of "pull requests", especially when the commit titles (acknowledging it looks up commit message for generating summaries) are not descriptive enough.
For example, sentences like "It also merges the beta branch into the refactor/typography-components-in-design-system branch." resulted from this.... see screenshot below for a summary that was generated for the stated pull request.
PR: #1438
Suggested solution
Prioritize the use of the pull request description for auto-summarization. I think Pull request descriptions typically provide a more comprehensive overview of the changes and goals of the pull request, which can lead to more informative and cleaner summaries.
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: