Truncate option for Discord

[echodreamz]

Feature Description

Would it be possible to add a setting that overrides the truncating of Discord webhook notifications? Previously, Gitea would push the entire commit message, now it cuts off at 50 characters like Github does, one of the reasons we stuck with Gitea is because the webhook notifications included the entire commit message.

Adding a setting (default to 50 characters) to enable/disable or extend the characters count I think would be a good middle ground to allow the previous behavior but also allow conforming to Github.

Screenshots

No response

[yp05327]

@kemzeb
Can you follow this?

[kemzeb]

Interesting, I never thought that there would be an interest in keeping the previous behavior. I think it would be fine to make this configurable, I'm just not sure how that would look. I'm also trying to ponder any potential problems in the future if we would introduce this setting. This would be a specific configuration, where it's:

• Just for Discord webhooks
• Just for push events

We also need to consider the scope of the setting, should it be:

• Instance-wide?
• Organization/repository-wide?

The easiest would be to define some instance-wide setting, but I'm unsure if this is the best option.

I do know that the webhook table does have a meta column and I originally thought that we could throw a simple flag in the table and in the Discord webhook creation form that would toggle truncation on/off. I then realized that this is actually used in order for us to communicate to Discord properly, so this won't work. Open to other ideas.

[echodreamz]

I would think an option on the webhook when creating it? Though, I'd assume this would require a new database column on the webhook table, so that might be a bit much?

For me, specifically, an instance-wide setting would be all I need, but that is just 1 use case.

[KonsXeni]

Wow, this post is fresh.

We concur in bringing this as a feature. It's very convenient for our small team.

I can't comment on bigger teams but I have a feeling it can still be beneficial, depending on the production structure.

It provides the much-needed awareness, and depending on your role the information can mean something different. Remote working environment.

[kemzeb]

Been busy but I'll see what I can do when I get the time. I may choose the "add new db column to webhook table" option for now as a way of storing webhook configurations, but I also want to check out the other forges to see if they implement something like this and if I can find a better approach.

[echodreamz]

Awesome! Looking forward to getting full discord notifications back :)

[echodreamz]

Has there been any traction on this?

[kemzeb]

I've been quite busy and wanted to do some other things in my backlog before setting my sights on this. I will get to working on this as soon as I can, but welcome anyone to open a PR if they can do it sooner :)

[IceTank]

Is this still being worked on? Having a way to display the entire commit message in the webhook like it was before would be very useful.

[echodreamz]

Agreed... This has really been a major loss to us. Enough to where we've disabled automatic updates to prevent future issues like this.