Integration status dashboard#176
Conversation
6221f2e to
f012938
Compare
0fb7d4c to
85b4d62
Compare
|
The created documentation from the pull request is available at: docu-html |
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
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
feb45de to
6f1ca70
Compare
6f1ca70 to
f24eb42
Compare
5e5f225 to
80355ee
Compare
There was a problem hiding this comment.
do we need to pin all the versions with commit hash here?
There was a problem hiding this comment.
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 .) |
There was a problem hiding this comment.
was wondering why I could not find the generated html file but it's pull_request_target :D
There was a problem hiding this comment.
should we migrate all the py scripts to be executable via bazel?!
There was a problem hiding this comment.
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 | |||
There was a problem hiding this comment.
we already have pygithub as a dep here. Could we use it instead of the custom api call?
Uh oh!
There was an error while loading. Please reload this page.