Skip to content

CI job to check that forks are in sync #20795

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 11, 2021

Conversation

acdlite
Copy link
Collaborator

@acdlite acdlite commented Feb 10, 2021

We don't always keep the reconciler forks in sync (otherwise it we wouldn't have forked it) but during periods when they are meant to be in sync, we use this job to confirm there are no differences.

@facebook-github-bot facebook-github-bot added CLA Signed React Core Team Opened by a member of the React Core Team labels Feb 10, 2021
@acdlite acdlite force-pushed the ci-check-sync-forks branch from 30d942f to 2b98224 Compare February 10, 2021 22:40
@sizebot
Copy link

sizebot commented Feb 10, 2021

Comparing: 9e9be6c...f7d9a5c

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name +/- Base Current +/- gzip Base gzip Current gzip
oss-stable/react-dom/cjs/react-dom.production.min.js = 122.22 kB 122.22 kB = 39.36 kB 39.36 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js = 128.81 kB 128.81 kB = 41.39 kB 41.39 kB
facebook-www/ReactDOM-prod.classic.js = 404.97 kB 404.97 kB = 75.14 kB 75.14 kB
facebook-www/ReactDOM-prod.modern.js = 393.32 kB 393.32 kB = 73.23 kB 73.23 kB
facebook-www/ReactDOMForked-prod.classic.js = 404.98 kB 404.98 kB = 75.14 kB 75.14 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against f7d9a5c

steps:
- checkout
- run: yarn workspaces info | head -n -1 > workspace_info.txt
- *restore_node_modules
Copy link
Member

Choose a reason for hiding this comment

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

If we got rid of glob and minimalist in the replace-fork script, we could skip these two steps to restore node_modules.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Would stamp that PR

We don't always keep the reconciler forks in sync (otherwise it we
wouldn't have forked it) but during periods when they are meant to be in
sync, we use this job to confirm there are no differences.
@acdlite acdlite force-pushed the ci-check-sync-forks branch from 539a6fb to f7d9a5c Compare February 11, 2021 00:08
@acdlite acdlite merged commit b593a6f into facebook:master Feb 11, 2021
koto pushed a commit to koto/react that referenced this pull request Jun 15, 2021
We don't always keep the reconciler forks in sync (otherwise it we
wouldn't have forked it) but during periods when they are meant to be in
sync, we use this job to confirm there are no differences.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed React Core Team Opened by a member of the React Core Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants