Skip to content

Conversation

aslushnikov
Copy link
Contributor

Currently, it might happen that two different patches clash for the
same build number for the browsers. In this case, authors might
not even know that they need to rebaseline.

This patch starts adding a second line to BUILD_NUMBER files - the
signature and date of the BUILD_NUMBER change. These are guaranteed
to clash, so it should not be possible to land patches without
re-baselining them.

@aslushnikov aslushnikov force-pushed the unconflict-build-numbers branch from 7e340dd to 694fc9d Compare July 2, 2020 06:06
@aslushnikov aslushnikov requested a review from dgozman July 2, 2020 06:07
Currently, it might happen that two different patches clash for the
same build number for the browsers. In this case, authors might
not even know that they need to rebaseline.

This patch starts adding a second line to `BUILD_NUMBER` files - the
signature and date of the `BUILD_NUMBER` change. These are guaranteed
to clash, so it should not be possible to land patches without
re-baselining them.
@aslushnikov aslushnikov force-pushed the unconflict-build-numbers branch from 694fc9d to 3a83fdb Compare July 2, 2020 19:05
@aslushnikov aslushnikov merged commit b1b6d3f into microsoft:master Jul 2, 2020
@aslushnikov aslushnikov deleted the unconflict-build-numbers branch July 2, 2020 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants