Update email.html to use "https://schema.org" instead of "http://schema.org"#3420
Merged
gotjosh merged 1 commit intoprometheus:mainfrom Aug 3, 2023
Merged
Update email.html to use "https://schema.org" instead of "http://schema.org"#3420gotjosh merged 1 commit intoprometheus:mainfrom
gotjosh merged 1 commit intoprometheus:mainfrom
Conversation
…ema.org" According to schema.org's faq both https and http are fine, but https is preferred going forward: https://schema.org/docs/faq.html#19 Why am I making this change? To make some security code scanner happy :) Signed-off-by: Alvin Lin <alvinlin123@gmail.com>
alvinlin123
changed the title
Member
|
Thank you very much for your contribution. |
alvinlin123
changed the title
simonpasquier
added a commit
to simonpasquier/alertmanager
that referenced
this pull request
Aug 3, 2023
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
simonpasquier
added a commit
to simonpasquier/alertmanager
that referenced
this pull request
Aug 4, 2023
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
simonpasquier
added a commit
to simonpasquier/alertmanager
that referenced
this pull request
Aug 4, 2023
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
gotjosh
pushed a commit
that referenced
this pull request
Aug 4, 2023
* Add template/email.tmpl to the clean target The change ensures that all assets can be regenerated from scratch in the CI. Signed-off-by: Simon Pasquier <spasquie@redhat.com> * Update email assets after #3420 Signed-off-by: Simon Pasquier <spasquie@redhat.com> --------- Signed-off-by: Simon Pasquier <spasquie@redhat.com>
gotjosh
pushed a commit
that referenced
this pull request
Aug 7, 2023
…ema.org" (#3420) According to schema.org's faq both https and http are fine, but https is preferred going forward: https://schema.org/docs/faq.html#19 Why am I making this change? To make some security code scanner happy :) Signed-off-by: Alvin Lin <alvinlin123@gmail.com>
gotjosh
pushed a commit
that referenced
this pull request
Aug 7, 2023
* Add template/email.tmpl to the clean target The change ensures that all assets can be regenerated from scratch in the CI. Signed-off-by: Simon Pasquier <spasquie@redhat.com> * Update email assets after #3420 Signed-off-by: Simon Pasquier <spasquie@redhat.com> --------- Signed-off-by: Simon Pasquier <spasquie@redhat.com>
radek-ryckowski
pushed a commit
to goldmansachs/alertmanager
that referenced
this pull request
Nov 6, 2023
…ema.org" (prometheus#3420) According to schema.org's faq both https and http are fine, but https is preferred going forward: https://schema.org/docs/faq.html#19 Why am I making this change? To make some security code scanner happy :) Signed-off-by: Alvin Lin <alvinlin123@gmail.com>
radek-ryckowski
pushed a commit
to goldmansachs/alertmanager
that referenced
this pull request
Nov 6, 2023
* Add template/email.tmpl to the clean target The change ensures that all assets can be regenerated from scratch in the CI. Signed-off-by: Simon Pasquier <spasquie@redhat.com> * Update email assets after prometheus#3420 Signed-off-by: Simon Pasquier <spasquie@redhat.com> --------- Signed-off-by: Simon Pasquier <spasquie@redhat.com>
qinxx108
pushed a commit
to amazon-contributing/alertmanager
that referenced
this pull request
Mar 28, 2024
…ema.org" (prometheus#3420) According to schema.org's faq both https and http are fine, but https is preferred going forward: https://schema.org/docs/faq.html#19 Why am I making this change? To make some security code scanner happy :) Signed-off-by: Alvin Lin <alvinlin123@gmail.com>
qinxx108
pushed a commit
to amazon-contributing/alertmanager
that referenced
this pull request
Mar 28, 2024
* Add template/email.tmpl to the clean target The change ensures that all assets can be regenerated from scratch in the CI. Signed-off-by: Simon Pasquier <spasquie@redhat.com> * Update email assets after prometheus#3420 Signed-off-by: Simon Pasquier <spasquie@redhat.com> --------- Signed-off-by: Simon Pasquier <spasquie@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
According to schema.org's faq both https and http are fine, but https is preferred going forward: https://schema.org/docs/faq.html#19
Why am I making this change? To make some security code scanner happy :)