Repository navigation
Release 0.4.0 - #188
Merged
Merged
Release 0.4.0#188
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.
Summary
0.4.0's headline is Spec runs:
thirdshift <Issue URL>on an issue with sub-issues now works through its Tickets, merging each into a Spec branch, and ends with a Spec PR that gets a Spec review, the Repair loop and, when asked, a Self-merge. It also adds a User config (~/.thirdshift/config.toml), written by the newthirdshift setup, and Run notifications by email through Resend.New commands
thirdshift setupwrites the User config with every setting at its default (Add thirdshift setup: write the defaults User config with no terminal #135). It suggests your GitHub or git email foremail.to(Setup: suggest the GitHub email for email.to #137), completes an existing config in place (Setup: edit an existing User config in place #138), and asks the Setup questions from a terminal (Setup: the questions from a terminal #151). The first Run from a terminal with no User config offers Setup (Offer Setup on the first Run from a terminal #162), and the installer's last line points to it (Setup: install output points to thirdshift setup #134).thirdshift email-test [<address>]sends one test email through Resend (thirdshift email-test through Resend #119).New and changed behaviour
parallel <n>orspec.parallel, default 3 (Parallel Tickets: spec.parallel and parallel <n> #163). A Spec run takes every Ticket it can reach and ends as a Failed spec run with a per-Ticket summary when any isn't done (Going as far as it can: Failed spec runs #155). The draft Spec PR opens once the first Ticket lands and carries a Tickets checklist (The draft Spec PR and its Tickets checklist #169). A Spec review runs before the Spec PR is marked ready (Spec review before the Spec PR is ready #164), then the Repair loop and, withmerge, a Self-merge (The Spec PR's Repair loop and Self-merge #171). An interrupt is passed on to the running Ticket's Run (Interrupting a Spec run #154). A Spec run sends one Run notification with a line per Ticket (One Run notification per Spec run #170).merge.alwaysand--no-merge(User config, with merge.always and --no-merge #116),logs.dir(Read logs.dir from the User config to set where session logs go #117),launch.pullfast-forwards the Launch directory's Base branch (Fast-forward the Launch directory's Base branch with launch.pull #125).--email [<address>]sends one when a Run ends, whatever the outcome (--email sends a Run notification whenever a Run ends #121).email.alwaysand--no-emailset and override the default (email.always and --no-email #124).closingIssuesReferences, which gh 2.45 lacks (Close the issue after a Self-merge unless it is already closed #186).Also: release tooling (#165, #166, #167, #168, #172, #173) and docs, glossary and prompts work (#101, #110, #123, #133, #140, #179, #184).
Version diff