Skip to content

chore: remove accidentally tracked build_hw/ directory#11583

Merged
sensei-hacker merged 1 commit into
iNavFlight:maintenance-10.xfrom
daijoubu:clean/remove-build-hw
May 25, 2026
Merged

chore: remove accidentally tracked build_hw/ directory#11583
sensei-hacker merged 1 commit into
iNavFlight:maintenance-10.xfrom
daijoubu:clean/remove-build-hw

Conversation

@daijoubu
Copy link
Copy Markdown
Contributor

Removes the build_hw/ directory (1.1GB, 27K files) that was accidentally committed as part of the HAL v1.3.3 update. These are cmake build artifacts and should not be tracked.

Also adds /build_*/ and /build_hw/ to .gitignore to prevent recurrence.

@qodo-code-review
Copy link
Copy Markdown
Contributor

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@sensei-hacker
Copy link
Copy Markdown
Member

Ugh. On the HAL PR I had written a comment saying "this PR seems to have 3000 extra files".
And then apparently clicked "merge" rather than "post comment".

@sensei-hacker sensei-hacker merged commit eb632b0 into iNavFlight:maintenance-10.x May 25, 2026
1 check passed
@daijoubu
Copy link
Copy Markdown
Contributor Author

I saw that comment, but then couldn't find it in the open PRs I was looking at too.

sensei-hacker added a commit to sensei-hacker/inav_unofficial_targets that referenced this pull request May 31, 2026
…t#11365

Conflict resolution in src/main/io/osd.c:
- Kept upstream's messages[8] (larger array for new geozone messages)
- Applied ADD_MSG() bounds-safe macro to upstream's relocated geozone block
- Took upstream's expanded NAV_ALTHOLD_MODE block with terrain follow
  messages (OSD_MSG_SURFACE_OK/BAD), using ADD_MSG() for all writes
- Removed osdCheckWarning/osdGetMultiFunctionMessage from osd.c
  (functions moved to fc/multifunction.c by upstream)

Applied ADD_MSG() protection to src/main/fc/multifunction.c where
upstream relocated the warning functions from osd.c.

Note: build_hw/ excluded — accidentally tracked upstream artifact,
see iNavFlight#11583 (fix pending for maintenance-9.x).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants