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
I personally think it would be better to have the different parts (changes and artifacts) in separate fields.
Downside would be a lower text length (Only 1000 characters) but this could be bypassed by having a new field with a zero-width space as title (\u200E) which is supported by Discord.
The biggest downside will be the total character length of 6000 characters per webhook, but this would also be an issue with just using the description, which limits the text to 2000 characters anyway.
I have a few suggestions to improve the overall display of the Discord Webhook which I list below
Link to a GitHub commit when available.
Right now are GitHub commits displayed like this:
While this isn't bad at all, does it miss out on a oportunity, to actually link to a GitHub Commit.
My suggestion is to link to the Commit itself.
Add option to use embedded links for Artifact jar.
Right now does the webhook display artifacts like this:
This can look horrible, if the link is quite long.
I suggest to add an option to have the link embedded like this:
Use actual embed fields instead of Description.
I personally think it would be better to have the different parts (changes and artifacts) in separate fields.
Downside would be a lower text length (Only 1000 characters) but this could be bypassed by having a new field with a zero-width space as title (
\u200E
) which is supported by Discord.The biggest downside will be the total character length of 6000 characters per webhook, but this would also be an issue with just using the description, which limits the text to 2000 characters anyway.
I made a very basic example using Leovoel's Embed Visualizer
The text was updated successfully, but these errors were encountered: