Conversation
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
mzanetti
force-pushed
the
pip-at-buildtime
branch
from
3b0b6fe to
5fd94ce
Compare
mzanetti
changed the title
mzanetti
force-pushed
the
pip-at-buildtime
branch
4 times, most recently
from
8dc4efe to
144dd70
Compare
mzanetti
force-pushed
the
pip-at-buildtime
branch
from
144dd70 to
2fad0b7
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
2 participants
nymea-plugins pull request checklist:
Make sure the pull request's title is of format "Plugin name: Add support for xyz" or "New plugin: Plugin name"
Did you test the changes on hardware, if not (e.g. absence of required hardware), please mention a person to confirm it has been tested.
Did you update the plugin's README.md accordingly?
Did you update translations (
cd builddir && make lupdate)?If you added a new plugin, should it be added to nymea-plugins-all or nymea-plugins-maker?