Skip to content

Integration status dashboard#176

Open
pawelrutkaq wants to merge 13 commits intoeclipse-score:mainfrom
qorix-group:pawelrutkaq_status_dashboard
Open

Integration status dashboard#176
pawelrutkaq wants to merge 13 commits intoeclipse-score:mainfrom
qorix-group:pawelrutkaq_status_dashboard

Conversation

@pawelrutkaq
Copy link
Contributor

@pawelrutkaq pawelrutkaq commented Mar 6, 2026

  • uses known_good.json to display current state
  • at generation checks a diff between the JSON and live status of main branches and embeed into report
  • allow insert PAT to always have a live preview of current state across all modules.
  • Set up the tooling root that will be used for moving the current tools refactorings into a single. maintanble codebase + UT and include them in workflows

@pawelrutkaq pawelrutkaq force-pushed the pawelrutkaq_status_dashboard branch from 6221f2e to f012938 Compare March 6, 2026 13:36
@pawelrutkaq pawelrutkaq force-pushed the pawelrutkaq_status_dashboard branch from 0fb7d4c to 85b4d62 Compare March 6, 2026 13:52
@github-actions
Copy link

github-actions bot commented Mar 6, 2026

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

Comment on lines +33 to +34
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Copy link
Contributor

Choose a reason for hiding this comment

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

why do we need it now?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

because I added a fetch during report generation so if user does not have PAT, it still see a diff in moment raport is generated

@pawelrutkaq pawelrutkaq force-pushed the pawelrutkaq_status_dashboard branch from feb45de to 6f1ca70 Compare March 6, 2026 14:10
@pawelrutkaq pawelrutkaq force-pushed the pawelrutkaq_status_dashboard branch from 6f1ca70 to f24eb42 Compare March 6, 2026 14:14
@pawelrutkaq pawelrutkaq force-pushed the pawelrutkaq_status_dashboard branch from 5e5f225 to 80355ee Compare March 6, 2026 14:31
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need to pin all the versions with commit hash here?

Copy link
Contributor

Choose a reason for hiding this comment

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

why do we track the MODULE.bazel.lock? should this be in .gitignore?

--github_user=${{ github.repository_owner }} \
--github_repo=${{ github.event.repository.name }}
CURRENT=$(realpath .)
Copy link
Contributor

Choose a reason for hiding this comment

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

was wondering why I could not find the generated html file but it's pull_request_target :D

Copy link
Contributor

Choose a reason for hiding this comment

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

should we migrate all the py scripts to be executable via bazel?!

Copy link
Contributor

Choose a reason for hiding this comment

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

what about wrapping gh cli? or do you want to be independent? gh cli is installed on every gh runner and also has the token

@@ -1 +1,2 @@
jinja2 >= 3
PyGithub>=2.1.1
Copy link
Contributor

Choose a reason for hiding this comment

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

we already have pygithub as a dep here. Could we use it instead of the custom api call?

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.

4 participants