License Header in PR notifications

[Dominik Riemer <do...@bytefabrik.ai>]

Hi,

should we remove the license header from the PR template? As it is included in every email in the body, it just makes reading PR info much more difficult, and I don't think there is any requirement to include the license header in PR notifications.
We could simply add the PR template file to the rat exclusions.

Cheers
DOminik

Re: License Header in PR notifications

[Florian Micklich <mi...@apache.org>]

+1 from me as well.
definitely an improvement for the eyes  ;)

Am Donnerstag, dem 12.01.2023 um 06:49 +0000 schrieb Philipp Zehnder:
> +1, yes I like the idea.<br>
> 
> Von: Dominik Riemer <[dominik.riemer@bytefabrik.ai](mailto:dominik.riemer@bytefabrik.ai)><br>
> Datum: Mittwoch, 11. Januar 2023 um 21:46<br>
> An: [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org) <[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)><br>
> Betreff: License Header in PR notifications<br>
> Hi,<br>
> 
> should we remove the license header from the PR template? As it is included in every email in the body, it just makes reading PR info much more difficult, and I don't think there is any requirement to include the license header in PR notifications.<br>
> We could simply add the PR template file to the rat exclusions.<br>
> 
> Cheers<br>
> DOminik<br>

AW: License Header in PR notifications

[Philipp Zehnder <ph...@bytefabrik.ai>]

+1, yes I like the idea.

Von: Dominik Riemer <do...@bytefabrik.ai>
Datum: Mittwoch, 11. Januar 2023 um 21:46
An: dev@streampipes.apache.org <de...@streampipes.apache.org>
Betreff: License Header in PR notifications
Hi,

should we remove the license header from the PR template? As it is included in every email in the body, it just makes reading PR info much more difficult, and I don't think there is any requirement to include the license header in PR notifications.
We could simply add the PR template file to the rat exclusions.

Cheers
DOminik