Skip to content

Conversation

@Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Mar 31, 2021

The changelog update script now prevents duplicate entries from being added. Specifically, it will ensure that if a PR has been referenced already in an entry, it will not add it again.

This should prevent it from adding duplicate entries for changes that were cherry-picked into hotfix releases.

Note that this duplication prevention only works for entries containing a PR number. We don't have any way to prevent duplicate entries yet in cases where we don't know the associated PR. We will be preventing this possibility entirely pretty soon in some upcoming release automation changes though, so I'm not concerned about this omission.

Relates to #10752

Manual testing steps:

  • Run yarn update-changelog
  • Look at the changelog
  • Run yarn update-changelog again
  • See that no entries including a PR number have been added a second time

@Gudahtt
Copy link
Member Author

Gudahtt commented Mar 31, 2021

This depends upon #10784

@Gudahtt Gudahtt force-pushed the prevent-duplicate-changelog-entries branch from d4a4cf4 to a52dfa7 Compare March 31, 2021 19:40
@metamaskbot
Copy link
Collaborator

Builds ready [a52dfa7]
Page Load Metrics (576 ± 50 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint47725884
domContentLoaded36374257410350
load36574357610350
domInteractive36374257410350

@Gudahtt Gudahtt force-pushed the prevent-duplicate-changelog-entries branch from a52dfa7 to 74e6a68 Compare March 31, 2021 22:43
@metamaskbot
Copy link
Collaborator

Builds ready [74e6a68]
Page Load Metrics (610 ± 37 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint45715673
domContentLoaded3877146087837
load3897156107837
domInteractive3877136087837

Base automatically changed from add-changelog-entries-under-correct-header to develop April 1, 2021 14:58
The changelog update script now prevents duplicate entries from being
added. Specifically, it will ensure that if a PR has been referenced
already in an entry, it will not add it again.

This should prevent it from adding duplicate entries for changes that
were cherry-picked into hotfix releases.

Note that this duplication prevention only works for entries containing
a PR number. We don't have any way to prevent duplicate entries yet in
cases where we don't know the associated PR. We will be preventing this
possibility entirely pretty soon in some upcoming release automation
changes though, so I'm not concerned about this omission.
@Gudahtt Gudahtt force-pushed the prevent-duplicate-changelog-entries branch from 74e6a68 to 2baac2a Compare April 1, 2021 14:59
@Gudahtt Gudahtt marked this pull request as ready for review April 1, 2021 15:02
@Gudahtt Gudahtt requested review from a team and kumavis as code owners April 1, 2021 15:02
@Gudahtt Gudahtt requested a review from brad-decker April 1, 2021 15:02
Copy link
Contributor

@brad-decker brad-decker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@metamaskbot
Copy link
Collaborator

Builds ready [2baac2a]
Page Load Metrics (658 ± 98 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint469964147
domContentLoaded397127165620598
load398127365820598
domInteractive397127165620598

@Gudahtt Gudahtt merged commit 1e562e9 into develop Apr 1, 2021
@Gudahtt Gudahtt deleted the prevent-duplicate-changelog-entries branch April 1, 2021 15:24
@github-actions github-actions bot locked and limited conversation to collaborators Apr 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants