Skip to content

Commit 934527c

Browse files
committed
fix: avoid having the AI use colors in slack changelogs
1 parent 42ce963 commit 934527c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

changelog_generator/ai_generator.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
"A Functional Changes section that should be understandable by readers that have no technical knowledge "
1313
"A section about possible regressions that could appear : this section should aim to be brief as it might be used during a production incident, but it musn't be too generic either"
1414
"A section about key kong/log metrics that should be observed during the production release process, these must be very precise"
15-
"The summary must be written with github and slack compatible markdown. It should be pleasing and give priority to salient points, must use colors and must use tasteful fonts, and follow best practices. You can use UML schemas and diagrams."
15+
"The summary must be written with github and slack compatible markdown. It should be pleasing and give priority to salient points. It may use emojis but no colors or fonts."
1616
"Do not print a description of each commit, the goal is to be as concise as possible. Do not take more than 200 words."
1717
"Do not try to infer the name and version of the release."
1818
)

0 commit comments

Comments
 (0)