Skip to content

add workflow to auto update the known_good#102

Open
kgraeper wants to merge 2 commits intoeclipse-score:mainfrom
etas-contrib:feature/update-known_good-to-latest-mains
Open

add workflow to auto update the known_good#102
kgraeper wants to merge 2 commits intoeclipse-score:mainfrom
etas-contrib:feature/update-known_good-to-latest-mains

Conversation

@kgraeper
Copy link
Contributor

No description provided.

@github-actions
Copy link

The created documentation from the pull request is available at: docu-html

@pawelrutkaq
Copy link
Contributor

lets proceed with it after 0.6 (22.02)

@FScholPer FScholPer added the v0.7 label Feb 19, 2026
@kgraeper kgraeper force-pushed the feature/update-known_good-to-latest-mains branch from a910811 to aa4d8a7 Compare February 27, 2026 13:57
uses: actions/upload-artifact@v4
with:
name: known_good.updated.json
path: known_good.updated.json
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These workflows shall call existing workflows that re-run on PR with changed know_good.json. Probbaly you shall trigger all existing workflows and they shall have conditonal step to change known good. We dont want to repeat workflows from PR but simply run them.

branches:
- feature/update-known_good-to-latest-mains
schedule:
- cron: '30 1 * * *' # Every night at 01:30 UTC on main branch
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make it every 1h minutes and simply stop if there is no dif in known good. Maybe we shall add manual trigger for now for testing ?

- name: not implemented
run: echo "Documentation generation not yet implemented here."

integration-test:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not needed or ? as said, the required jobs are jobs from PR

Copy link
Contributor

@pawelrutkaq pawelrutkaq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Questions: shall all our PR workflows be changed to a workflow_call and we shall have an one PR workflows that calls all the others ? This way in these workflows you also could easily call PR workflow and you are done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants