Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a demo of the page at https://modern-python.github.io/release-scope/ for people who want to try it without GitLab or Jira.
How it is built
demo/scenario.pydescribes a made-up shop group with four services (api,web,worker, andadmin, which is fully deployed) and six Jira issues.demo/build.pymocks GitLab and Jira with respx routes generated from that scenario and runs the realcollectcommand, so the page andreport.jsonalways come from the current code and schema. A hand-writtenreport.jsonwould drift silently on every schema bump.The scenario covers the states worth seeing: tags ahead of production, untagged changes, a failed and a running pipeline, staging deployments, an issue spanning two services, issues that ship anyway, and links that are open, closed, in production, or in a project outside the report. Dates are relative to build time, so the demo looks current. Every link points to
example.comand goes nowhere.Publishing
.github/workflows/demo.ymlbuilds and deploys on each stable release tag, plus a manual trigger. Pages is already enabled for the repo (source: GitHub Actions), and thegithub-pagesenvironment now accepts tags matching*.*.*as well asmain.Checks
just demobuilds intosite/(already gitignored);just demo-serveserves it on port 8000.demo/is not in the wheel.