Create build repo or branch from each commit to trunk to aid git bisects. #57897
peterwilsoncc
started this conversation in
Developer Experience
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As the Gutenberg repo makes heavy use of NPM dependencies, it makes a
git bisect
difficult as one needs to runnpm i; npm run build
during each step. For short time frames running thewatch
command may work but for the initial commit to WordPress-Develop during the release cycle, it usually is not.When running a
git bisect
on WordPress-Develop, it's possible to use https://github.com/wordPress/wordpress to find the reference without the need to run a build on each step.For debugging purposes, I think maintaining a build repo or branch of Gutenberg would be helpful. Each commit to
trunk
(and possiblywp/*
branches) would improve thebisect
workflow and improve the accuracy.The commit message format for the build repo would be similar to WordPress/WordPress commit logs:
cc @gziolo @adamziel
Beta Was this translation helpful? Give feedback.
All reactions