This repository was archived by the owner on Oct 17, 2026. It is now read-only.
Repository navigation
chore: adopt the Common Tools app standard - #12
Merged
Merged
Conversation
The repository files, scripts, and release steps had drifted from the other Common Tools apps, and nothing reported it.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
This app's repository files had drifted from the other Common Tools apps:
scripts/task;Nothing reported drift.
Approach
Applied the Common Tools app standard from oddurs/common-tools (
standard/), now checked daily by its Standard workflow.scripts/agent,setup,task,dev-cert,release;scripts/task test <name>,package(dist/) andrun(build, quit, relaunch). The build reads the deployment target from Info.plist and signs with the shared "Common Tools Development" identity when it's present (scripts/dev-cert).scripts/release <version>: CHANGELOG fold, version bump, ship, tag the merge, wait, verify the download. The release workflow checks the tag matches Info.plist and publishes the CHANGELOG section as the notes.node scripts/standard.js checkin common-tools passes against this branch.Look at sceptically
scripts/releasehasn't run end to end yet. The first release will be its test.scripts/dev-cert.