Repository navigation
[Question]: How should contributors without a SIMATIC AX license contribute ST code? #88
Description
Your Question
Hi! I've contributed some docs and CI fixes (simatic-ax/statemachine#81, simatic-ax/template-app#73, simatic-ax/template-library#77) and would like to help with library code next, e.g. simatic-ax/conversion#76–#78.
I don't have a SIMATIC AX license, so I can't run apax build / apax test locally. The CI on fork PRs can't run either, because APAX_TOKEN isn't available to forks.
What's the preferred way to handle this? Is it okay to submit ST changes with unit tests that I couldn't run myself, and have a maintainer build and test them? Or would you rather only receive code contributions from people who can test locally?
I'm doing this in my spare time, so no pressure. I'd just like to know what's useful for you before I spend time on it.
Version
No response
Additional Context
No response
Research
- I have searched the existing issues and discussions
- I have read the documentation
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
BeckerStS commentedon Oct 14, 2026
Hi @karakoc49
first of all : good to have you with us here on this space and thanks for contributing.
We will have a look on your PRs once we plan to introduce the next batch of changes due to product updates that will hit the community packages very soon.
Besides that, we understand that external contribution requests currently feels a little bit odd.
This is caused by various reasons : mainly due to ongoing legal implications, access to the tool chain itself and the fact that SIMATIC AX currently is still in an limited release state.
However ... we currently working on all these fronts in order to deliver you all a better non-org-scoped community experience for the content in the future. This may include providing publicly available runner images / workflows / actions you can use once you have your own APAX product-token available to let these workflows run on your organization/ space of the clone.
Atm. we would prefer code-contributions to excising projects or new repos from within the organization cause otherwise we have to introduce the changes to our space prior in order to let the pipelines run and validate. TBH not a fan of playing ping-pong, though ;-)
Again ... we hope this situation will change and we can update you on this sooner than later.
Anyway, any kind contribution is highly welcomed which ultimately helps the CODEOWNER making better decisions and faster adjustments.
Greetings from the SIMATIC AX - GH Community Admin Team
Happy coding.