At a previous employer we did this with our docs repo.
The public docs site was managed and deployed via a private GitHub repository, and we had a public GitHub repo that mirrored it.
The link between them was an action on the private repo that pushed each new man commit to the mirror. Customer PRs on the public mirror would be merged into the private repo, auto synced to the mirror, and GH would mark the public PR as merged when it noticed the PR commits were all on main.
It was a bit of a headache, but worked well enough once stag involved in docs built up some workflow conventions. The driver for the setup was the docs writers want the option to develop pre-release docs discretely, but customer contributions were also valued.
Interesting! May I ask what area you lived in (not due to the power distributor, but the age of the infrastructure in the area). The areas I've had issues are Brunswick, Thornbury and Footscray. Folks at work (we're a bit spread out but mostly Melbourne based) often talk of minor outages etc...
I actually had some electronics fail quite recently after a number of minor outages and speaking with insurance they were saying it's very common in certain areas where the infrastructure is aging or has recently been struck by lightening.
I have noticed the operating voltage in the inner north seems to vary between as low as 217V to 246V, but it's quite frequent you notice the lights dimming in houses round here. I don't think there were any last summer (if you could call it a summer) but usually I'd experience 2-5 (ish) complete outages on hot days, when I spoke to someone in know they said this is normal as they load shed you can experience short outages.
Load shedding is quite rare, I believe the only instance recently in Melbourne was on the 13th of February when several transmission towers carrying the Moorabool-Sydneham 500kV circuits were destroyed in the severe storms that day, and load-shedding was required to keep the system in a secure state.
Outages are almost always due to faults in the local distribution network.
There are 5 different businesses that own and operate the distribution network in different parts of Melbourne (AusNet, Jemena, Citipower, Powercor and United Energy).
AusNet owns & maintains the transmission network in Victoria, but it is under the operational control of AEMO.
Dispatch of generation and FCAS instructions is NEM-wide and the responsibility of AEMO.
Interesting that there are so many different businesses responsible for supplying electricity in Melbourne. This might explain why several people have mentioned having different experiences with the reliability of the grid in Melbourne. In Chicago, Commonwealth Edison is responsible for the entirety of the grid.
Thanks! I'll compare with Route53 mentioned above and decide the way forward. I was quite happy with Gandi's similar no bullshit approach for the past few years until the abrupt mailbox change last year.
Implicit or explicit, I’m OK with the global namespace.
On paper it’s awkward, but in reality convention and social norms make it rarely an issue.
The global namespace only supporting exactly one version of each gem encourages a health culture of stable ABIs and deprecation periods too. An absolute dream compared to some language ecosystems
The public docs site was managed and deployed via a private GitHub repository, and we had a public GitHub repo that mirrored it.
The link between them was an action on the private repo that pushed each new man commit to the mirror. Customer PRs on the public mirror would be merged into the private repo, auto synced to the mirror, and GH would mark the public PR as merged when it noticed the PR commits were all on main.
It was a bit of a headache, but worked well enough once stag involved in docs built up some workflow conventions. The driver for the setup was the docs writers want the option to develop pre-release docs discretely, but customer contributions were also valued.