Add ability to run as a service, metrics endpoint and dev helper scripts - #45
Open
richcq wants to merge 1 commit into
Open
Add ability to run as a service, metrics endpoint and dev helper scripts#45richcq wants to merge 1 commit into
richcq wants to merge 1 commit into
Conversation
richcq
marked this pull request as ready for review
September 10, 2026 17:12
richcq
force-pushed
the
feat/run-as-service-add-metrics
branch
from
September 11, 2026 05:05
202046e to
1d1c8ea
Compare
…s and dev helper scripts
richcq
force-pushed
the
feat/run-as-service-add-metrics
branch
from
September 11, 2026 05:09
1d1c8ea to
f7044c4
Compare
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
1 participant
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.
Adds the ability to run this a lightweight container with the addition of
/metricsand/healthendpoints as my goal was to expose some GitHub Component metrics to an observability platform; in my use-caseDatadogso I can construct some customdashboardsandalertsaround the live and previous state of GitHub components.It made more sense to add it to this project than spin up a another project for what is essentially a metrics endpoint and running in a container, whilst retaining the existing deployment pattern of
GitHub Pagesintact.The
scripts/*are untouched, this adds a semi-lightweightserverimplementation and a few development helper scripts.Note
I am aware that the
atomfeed is used as the source of truth using thegithistory, so obviously theflatandparseworkflows will need to continue to run to keep the realgithistory for these correct/fresh. In theory as long as the container keeps running and the internalgithistory (never pushed) is updated it can keep running for quite some time without a re-publish/redeployment.