Can you auto push autopilotmega.xml on a schedule to mavlink/mavlink?

[hamishwillee]

We just got a clash in mavlink#2174 because development.xml was assigned an ID that was used by ArduPilotmega.xml some months ago.

Now the value development was defined in the wrong range but would be good if we could catch earlier.

Having most up to date dialects would help with that. Is it possible to push ardupilotmega up on a cycle using a workflow?

[Davidsastresas]

I second this, thanks @hamishwillee. For awareness @rmackay9

[hamishwillee]

@peterbarker I fixed this using a workflow in mavlink/mavlink - mavlink#2177, resulting in first PR mavlink#2178

This just fetches ardupilotmega.xml, but that dialect depends on a number of others (loweheiser.xml) is new to me. Which of these are managed as part of the ardupilot project? I.e. the "master" version is seen to be the one in ArduPilot/mavlink.

  <include>uAvionix.xml</include>
  <include>icarous.xml</include>
  <include>loweheiser.xml</include>
  <include>cubepilot.xml</include>
  <include>csAirLink.xml</include>

[hamishwillee]

A bit messy - just got caught because MAV_CMD_EXTERNAL_POSITION_ESTIMATE moved into common upstream, but not here - so we ended up with clashes.

[khancyr]

I think this is possible technically. One issue is that GitHub disable programmed action if the repo has low or no activity for some time...but we should be able to manage this.

I will try to look on this issue to maintain a sync between repos

[Davidsastresas]

That would be awesome, thank you @khancyr!

[hamishwillee]

Thanks @khancyr - if you or @auturgy or @amilcarlucas can keep this repo in-sync with the upstream repo (as far as you) can that would be great (I am then happy to pull the ardupilot-managed xml up to mavlink/mavlink on a schedule).

On way to do this is how PX4 takes the mavlink repo. There is a scheduled github action that creates a PR and updates it with any changes (if there are any). The PR sits there being updated for weeks/months until someone is ready to merge.
YOu could do this similarly, and then review/do late fixes before merging.