Commits
Branch selector
User selector
Datepicker
Commit History
Commits on Sep 25, 2024
Commits on Sep 24, 2024
Commits on Sep 23, 2024
Commits on Sep 20, 2024
Commits on Sep 19, 2024
Commits on Sep 13, 2024
Commits on Sep 12, 2024
Commits on Sep 10, 2024
Commits on Sep 9, 2024
Commits on Sep 6, 2024
Commits on Sep 4, 2024
Commits on Aug 30, 2024
<img width="309" alt="Screenshot 2024-08-30 at 3 46 35 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/4d7d4cb0-ce2e-4cdd-bbdb-90de1347a77b">" class="color-fg-default" href="https://github.com/vercel/next.js/commit/e8512b3194838d2a223a024d4048f946d506da73">fix(CI): Don't require the GRAPHITE_TOKEN secret, as it's not available in forks (#69517 <img width="309" alt="Screenshot 2024-08-30 at 3 46 35 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/4d7d4cb0-ce2e-4cdd-bbdb-90de1347a77b">" class="color-fg-default" href="https://github.com/vercel/next.js/commit/e8512b3194838d2a223a024d4048f946d506da73">)
Commits on Aug 29, 2024
fix(turbopack-ecmascript-plugins): Accept a partial object for StyledComponentsTransformConfig (#69474)
And see that most jobs are skipped, leaving us with a very small set of test jobs: <img width="875" alt="Screenshot 2024-08-26 at 4 21 53 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/91623d84-b4b7-4d00-8177-37ffbf773046"> ### Observed Failure at Top of Stack Even though the failure is caused by the middle of the stack, a documentation-only change at the top of the stack still catches the failure caused by the middle of the stack, as the "documentation only" check compares against canary, not just the parent PR in the stack. <img width="1713" alt="Screenshot 2024-08-26 at 4 24 27 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/dd2ba177-8579-42c7-a602-56d03732f44d"> ### Bypassing CI Optimization Add the new label to the PR in the middle of the stack, and force it to re-run by making a change to the commit message and re-submitting with `gh submit`. <img width="468" alt="Screenshot 2024-08-26 at 4 26 49 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/c04b0379-b4f4-4d83-b41b-a1aa3a297f8d"> See that the debug output shows the label being detected: <img width="416" alt="Screenshot 2024-08-26 at 4 35 11 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/a2828f49-7a76-4266-ba7c-de370045bcb5"> And see that the full CI suite runs!" class="color-fg-default" href="https://github.com/vercel/next.js/commit/5fb091c171707834048f3db92cc17d0926d43fcf">chore(CI): Use Graphite's CI Optimization Feature (#69204 And see that most jobs are skipped, leaving us with a very small set of test jobs: <img width="875" alt="Screenshot 2024-08-26 at 4 21 53 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/91623d84-b4b7-4d00-8177-37ffbf773046"> ### Observed Failure at Top of Stack Even though the failure is caused by the middle of the stack, a documentation-only change at the top of the stack still catches the failure caused by the middle of the stack, as the "documentation only" check compares against canary, not just the parent PR in the stack. <img width="1713" alt="Screenshot 2024-08-26 at 4 24 27 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/dd2ba177-8579-42c7-a602-56d03732f44d"> ### Bypassing CI Optimization Add the new label to the PR in the middle of the stack, and force it to re-run by making a change to the commit message and re-submitting with `gh submit`. <img width="468" alt="Screenshot 2024-08-26 at 4 26 49 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/c04b0379-b4f4-4d83-b41b-a1aa3a297f8d"> See that the debug output shows the label being detected: <img width="416" alt="Screenshot 2024-08-26 at 4 35 11 PM" src=https://github.com/vercel/next.js/"https://github.com/user-attachments/assets/a2828f49-7a76-4266-ba7c-de370045bcb5"> And see that the full CI suite runs!" class="color-fg-default" href="https://github.com/vercel/next.js/commit/5fb091c171707834048f3db92cc17d0926d43fcf">)