You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, GitHub isolates caches by branch. With the newest CI rework, the first run of new PRs will always have a cache miss right now, causing it to build everything from scratch. That's annoying. PR builds can use caches created by the base or default branch (in our case usually the same). So the accepted workaround is that the default branch will run a job just to build a cache for all PRs.
This is not trivial to do with our setup. I'm not yet sure how one would best approach it.
Unfortunately, GitHub isolates caches by branch. With the newest CI rework, the first run of new PRs will always have a cache miss right now, causing it to build everything from scratch. That's annoying. PR builds can use caches created by the base or default branch (in our case usually the same). So the accepted workaround is that the default branch will run a job just to build a cache for all PRs.
This is not trivial to do with our setup. I'm not yet sure how one would best approach it.
Context: https:/orgs/community/discussions/27059
The text was updated successfully, but these errors were encountered: