Skip to content

Conversation

HTRamsey
Copy link
Collaborator

Closes #12920

@HTRamsey HTRamsey marked this pull request as ready for review June 16, 2025 15:49
@HTRamsey HTRamsey requested a review from DonLakeFlyer June 16, 2025 15:49
@HTRamsey HTRamsey force-pushed the dev-mavlink-docs branch 2 times, most recently from b914c64 to 3f5d1dd Compare June 16, 2025 16:23
@DonLakeFlyer
Copy link
Contributor

DonLakeFlyer commented Jun 16, 2025

Can you set QGC_MAVLINK_GIT_REPO to a local repo on your hard disk somehow? file:// ? I think that's what happen when folks are developing something new in mavlink.

@HTRamsey
Copy link
Collaborator Author

Good point, I will add that too

@HTRamsey
Copy link
Collaborator Author

@DonLakeFlyer done

@HTRamsey HTRamsey merged commit b34e3f1 into mavlink:master Jun 18, 2025
3 checks passed
@HTRamsey HTRamsey deleted the dev-mavlink-docs branch June 18, 2025 17:16
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.

Docs 5.0: Update how to change mavlink repo tag

2 participants