New vehicle action

[rligocki]

No description provided.

[JonasVautherin]

What are those cmake.yml for? 🤔

[julianoes]

@rligocki should we try another effort to get this in?

[rligocki]

Let's do it. But I will need little bit of guidance.

[julianoes]

@rligocki I've squashed all your commits into one, and removed the files you had added by accident. We now need to add the actual implementation back in. I suggest you fetch this state and add a commit on top with the implementation.

The way to get to this state (without ugly merges) would be:

The steps below assume that origin is your fork:

git stash # to get rid of anything dirty in your tree, in case you need it later
git fetch origin
git checkout main
git reset --hard origin/main

This should wipe your changes and reset to the state of this PR. Note that it does not have any of the actual implementation here. So if you have that one somewhere locally, make sure to stash it or put it into a branch to use it later.

[rligocki]

Now it should contain implementation and tests. This should work without any problem for 1.12 and 1.11 version of PX4. Only update of proto needs to be done.

[julianoes]

@rligocki this is still conflicting, see what GitHub says: ⬇️.

[rligocki]

CI did not passed. Is it possible that it is caused by merge requests, that has been done?

[rligocki]

Based on latest CI from main branch, it looks like PX4 1.12 tests failed because of latest commits in main branch.

[rligocki]

Now it should be ok.

[julianoes]

@rligocki CI seems to fail the new test, any idea?

[  FAILED  ] SitlTest.MissionTakeoffAndLand

https://github.com/mavlink/MAVSDK/runs/5014636341?check_suite_focus=true#step:4:47103

[julianoes]

Looks good. I'll merge it next time I go through all PRs.

[julianoes]

Rebased and force pushed.

[julianoes]

Thanks @rligocki and sorry it took a while.