Title: Track output of `check_versions.py` in a GitHub Actions workflow's job summary · Issue #170 · python/docsbuild-scripts · GitHub
Open Graph Title: Track output of `check_versions.py` in a GitHub Actions workflow's job summary · Issue #170 · python/docsbuild-scripts
X Title: Track output of `check_versions.py` in a GitHub Actions workflow's job summary · Issue #170 · python/docsbuild-scripts
Description: What would change? Add a GitHub Actions workflow that regularly runs check_versions.py, and use the "job summary" feature to make that visible in a more prominent location. This would allow linking to the workflow's page from the README,...
Open Graph Description: What would change? Add a GitHub Actions workflow that regularly runs check_versions.py, and use the "job summary" feature to make that visible in a more prominent location. This would allow linking...
X Description: What would change? Add a GitHub Actions workflow that regularly runs check_versions.py, and use the "job summary" feature to make that visible in a more prominent location. This would all...
Opengraph URL: https://github.com/python/docsbuild-scripts/issues/170
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Track output of `check_versions.py` in a GitHub Actions workflow's job summary","articleBody":"### What would change?\r\n\r\nAdd a GitHub Actions workflow that regularly runs `check_versions.py`, and use the \"job summary\" feature to make that visible in a more prominent location. This would allow linking to the workflow's page from the README, where the user can click into one of the jobs and see the version table as a \"job summary\".\r\n\r\nhttps://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary\r\n\r\nThe link from the README would be similar to [this one for pypi-package.yml](https://github.com/python/python-docs-theme/actions/workflows/pypi-package.yml?query=branch%3Amain), and the job summary would be a markdown block presented like [Build \u0026 verify package summary](https://github.com/python/python-docs-theme/actions/runs/6432027811#summary-17466044006) (this example uses `\u003cdetails\u003e` for dropdowns, and also attaches artifacts which are shown above the summary -- we likely wouldn't do either of those things).\r\n\r\n### What is the benefit of this?\r\n\r\nThis would eliminate the need for follow up bump PRs like #156 in the future, since the information would be automatically tracked and kept up to date via the regular re-runs of the script (with historical information as well, which is a nice side-effect?).\r\n","author":{"url":"https://github.com/pradyunsg","@type":"Person","name":"pradyunsg"},"datePublished":"2023-10-07T19:49:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/170/docsbuild-scripts/issues/170"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:c896f036-1518-dcca-4357-97ce7f121183 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | ACDC:192DFC:648DE69:88B6B47:696E3B3D |
| html-safe-nonce | 0a0c4da07e609d9ddae1438c52534d05142406884c3f453a1e77b0a1f77ab279 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBQ0RDOjE5MkRGQzo2NDhERTY5Ojg4QjZCNDc6Njk2RTNCM0QiLCJ2aXNpdG9yX2lkIjoiNTQ4NjAxNDkwOTIzNDY5MDg3NyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 262a713b64e99bdfdbc858f51ba5c20eaccc35e11a9aee32928e55bca4933703 |
| hovercard-subject-tag | issue:1931480387 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/python/docsbuild-scripts/170/issue_layout |
| twitter:image | https://opengraph.githubassets.com/e91dedd2ae9906fe24d3971cd0c6a29f161e6071c00a80e844be19c94ef89851/python/docsbuild-scripts/issues/170 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/e91dedd2ae9906fe24d3971cd0c6a29f161e6071c00a80e844be19c94ef89851/python/docsbuild-scripts/issues/170 |
| og:image:alt | What would change? Add a GitHub Actions workflow that regularly runs check_versions.py, and use the "job summary" feature to make that visible in a more prominent location. This would allow linking... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | pradyunsg |
| hostname | github.com |
| expected-hostname | github.com |
| None | b39958d54b39d52b9fc890ff25687d2383a83e003512d4480499b2dbd046839f |
| turbo-cache-control | no-preview |
| go-import | github.com/python/docsbuild-scripts git https://github.com/python/docsbuild-scripts.git |
| octolytics-dimension-user_id | 1525981 |
| octolytics-dimension-user_login | python |
| octolytics-dimension-repository_id | 23553472 |
| octolytics-dimension-repository_nwo | python/docsbuild-scripts |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 23553472 |
| octolytics-dimension-repository_network_root_nwo | python/docsbuild-scripts |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | fba10be4ea34590240b2f4a625fc807362c2d5b8 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width