Repository navigation
Release 0.8.0 - #335
Merged
Merged
Release 0.8.0#335
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.8.0 is about Weeding (#332): a crontab line can now run
thirdshift architect base <branch>every few minutes withmerge.always, and each pass is safe and quiet. It adds no new command, daemon or flag.architect-ideaandneeds-triage, keeping its other labels, and that includes an idea that was already filed. While such an idea is open withneeds-triage, later Architect runs are skipped: they exit0, print the idea's URL on stdout and the reason on stderr. Takingneeds-triageoff or closing the issue releases the pause. If labelling fails, the review fails with one notification that carries the cause.ready.rs, with no Sweep and no Claim limit. Aready-for-agentissue with no Pickup line to take it keeps Architect runs from starting.emailoremail.alwaysasked for one. A broken notification setup still exits1before the skip. A skipped run's line stays in the scheduler's log.Also: README Weeding section and sample crontab line (#334).
Version diff