Skip to content

New workflow#72

Open
t-persson wants to merge 4 commits intoeiffel-community:mainfrom
t-persson:new-workflow
Open

New workflow#72
t-persson wants to merge 4 commits intoeiffel-community:mainfrom
t-persson:new-workflow

Conversation

@t-persson
Copy link
Collaborator

Applicable Issues

Won't work until: #71 is merged since this depends on the release event.
eiffel-community/etos#499

Description of the Change

This workflow will be triggered if the actions for publishing etos-test-runner to pypi succeeds and the workflow will then create a pull request on the ETOS repository with the image updates. The workflow will use the text body of the release published in the ETOS Test Runner.

Because we do not publish to Pypi for each commit in this repository we cannot use exactly the same workflow as we are in the other repositories. We would need to create a release (see #71 ) which would trigger this workflow and we extract the tag from it and the body of the release to be used in the ETOS pull request.

Alternate Designs

We could do the push directly to main in the ETOS repository, but I like the idea of being able to "freeze" the ETOS repository if necessary by not merging pull requests. I also have an aversion to giving those permissions out in the service repositories.
I am still using fjogeleit/yaml-update-action which feels quite unnecessary now that we don't use it for anything but running "yq", but we know that it works so I don't mind it that much.

Possible Drawbacks

We need to create an app in the eiffel-community (already done) and add the private key and app ID to this repository secrets for it to work. I could not find any other way of creating pull requests than doing it this way. We can add SSH-keys to the secrets that can be used as DEPLOY_KEY but we cannot create pull requests using that.

Sign-off

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Signed-off-by: Tobias Persson tobias.persson@axis.com

@t-persson t-persson requested a review from a team as a code owner February 18, 2026 09:02
@t-persson t-persson requested review from andmat900 and fredjn and removed request for a team February 18, 2026 09:02
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.

2 participants