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
When NuttX merges our PR, the Merge Job won't run until 00:00 UTC and 12:00 UTC. How can we be really sure that our PR was merged correctly?
Let's create a GitHub Org (at no cost), fork the NuttX Repo and trigger the CI Workflow. (Which won't charge any extra GitHub Runner Minutes to NuttX Project!)
Head to our GitHub Dashboard. Create a New Organisation. Give it any name (probably your GitHub ID appended with 2)
Browse to NuttX Repo. Click Fork and select our GitHub Org.
We enable GitHub Actions (which won't be charged to NuttX Project)
master branch will no longer auto-build when we sync with upstream. To fix this: We rename master branch to releases/master...
(Note: master branch in the screenshots should be releases/master instead)
(Actually the Commit History will look messy if we do the above, and Discard Commit won't appear. I prefer to keep the master branch, and run this script to enable builds)
Head back to GitHub Actions to Check the CI Workflow
(Note: master branch in the screenshots should be releases/master instead)
When We Merge Another PR: Click Sync Fork > Discard Commits. CI Workflow will auto-start (no need to create a file to trigger it)
(Note: master branch in the screenshot should be releases/master instead)
If "Discord Commits" doesn't appear: Click "Update Branch". (See the "Messy Commit History" comment above)
For The Next Update: Click Sync Fork > Update Branch
To Run macOS and Windows Jobs: Edit .github/workflows/build.yml. Modify the 4 references to arch.yml, point them to our GitHub Org at releases/master branch:
Optional: Disable fail-fast so that it runs all builds, regardless of error. Remove max-parallel so that it will use unlimited concurrent runners. Edit .github/workflows/build.yml, change...
What about nuttx-apps? Just fork nuttx repo (not nuttx-apps) and trigger the CI Workflow, the exact same way as above. The CI Workflow will checkout and compile apache/nuttx-apps, which contains the NuttX Apps that we have merged.
(See Also: How to run CI Checks on a PR before Submission)
When NuttX merges our PR, the Merge Job won't run until 00:00 UTC and 12:00 UTC. How can we be really sure that our PR was merged correctly?
Let's create a GitHub Org (at no cost), fork the NuttX Repo and trigger the CI Workflow. (Which won't charge any extra GitHub Runner Minutes to NuttX Project!)
Head to our GitHub Dashboard. Create a New Organisation. Give it any name (probably your GitHub ID appended with
2
)Browse to NuttX Repo. Click Fork and select our GitHub Org.
We enable GitHub Actions (which won't be charged to NuttX Project)
master
branch will no longer auto-build when we sync with upstream. To fix this: We renamemaster
branch toreleases/master
...Browse to our NuttX Repo, click Settings > Default Branch > Rename Branch >
releases/master
To trigger the CI Workflow, we Create a File
(Note:
master
branch in the screenshots should bereleases/master
instead)(Actually the Commit History will look messy if we do the above, and Discard Commit won't appear. I prefer to keep the
master
branch, and run this script to enable builds)Head back to GitHub Actions to Check the CI Workflow
(Note:
master
branch in the screenshots should bereleases/master
instead)When We Merge Another PR: Click Sync Fork > Discard Commits. CI Workflow will auto-start (no need to create a file to trigger it)
(Note:
master
branch in the screenshot should bereleases/master
instead)If "Discord Commits" doesn't appear: Click "Update Branch". (See the "Messy Commit History" comment above)
For The Next Update: Click Sync Fork > Update Branch
To Run macOS and Windows Jobs: Edit .github/workflows/build.yml. Modify the 4 references to arch.yml, point them to our GitHub Org at
releases/master
branch:Then edit .github/workflows/arch.yml. Delete this section:
(Or use a script like this)
Optional: Disable
fail-fast
so that it runs all builds, regardless of error. Removemax-parallel
so that it will use unlimited concurrent runners. Edit .github/workflows/build.yml, change...To...
(Like this)
What about nuttx-apps? Just fork
nuttx
repo (notnuttx-apps
) and trigger the CI Workflow, the exact same way as above. The CI Workflow will checkout and compileapache/nuttx-apps
, which contains the NuttX Apps that we have merged.nuttx/.github/workflows/build.yml
Lines 102 to 110 in e75ac11
(That's why we don't need a Scheduled Merge Job for
nuttx-apps
. Everything is already inside the Scheduled Merge Job fornuttx
)The text was updated successfully, but these errors were encountered: