📝 npm-publish GitHub Packages workflow 1 commit 19d ago minor change
pdombkins/mikeOSS_Australia
An Australia-branded take on Mike, currently laying the plumbing to publish itself as an installable package.
This is pdombkins's fork of Mike, carrying an Australian flag in its name. If you tried it today you'd find something very close to upstream Mike - the divergence so far is a single thread of work, and it's behind the scenes rather than in the product a reader would touch.
That one thread is about distribution: pdombkins has wired up automated package publishing, so that when a release is cut, the build gets tested and pushed to GitHub's package registry for others to install. It's the kind of groundwork you do when you're planning to hand a package to teammates or downstream users rather than just running from source.
Who's behind it and where it's headed is still mostly implied by the name. Beyond the Australia branding, there's no niche or client story spelled out yet - this reads like the opening move of a fork getting its release pipeline in order before the interesting product work begins.
What's in it
- Australia branding The fork carries an Australian identity in its name, though what that focus means in practice isn't spelled out yet.
- Automated release publishing When a release is cut, the build is tested and pushed to GitHub's package registry - groundwork for shipping this as an installable package rather than source you clone.
Direction
infrastructurebranding