fix(rebrand): full-cutover rename miner/AMS per-repo and operator config filenames - #5765
Merged
Conversation
…fig filenames
Renames the two remaining unrenamed config-file surfaces in the miner
package: .gittensory-miner.yml/.json (per-target-repo miner goal spec,
MINER_GOAL_SPEC_FILENAMES) and .gittensory-ams.yml/.json (the
operator-local AMS execution policy, AMS_POLICY_SPEC_FILENAMES) become
.loopover-miner.* / .loopover-ams.*, along with their .env sibling and
all four checked-in .example files, .gitignore entries, and the
docker-compose.miner.yml env_file directive that actually loads one of
them at runtime.
Also fixes directly-adjacent stale prose in prometheus/rules/alerts.yml
(a runbook CLI-command example and .gittensory-ams.yml path mentions).
Deliberately not touched: the Prometheus rule *group* names
(gittensory-miner-prediction/-portfolio-queue/-governor) and the
up{job="gittensory"} scrape-job label in the same file, and the ~150+
"gittensory-miner" mentions in test describe()/tmpdir-prefix strings
across the suite -- distinct, larger-blast-radius surfaces than a
config-filename rename, left for a dedicated follow-up.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5765 +/- ##
=======================================
Coverage 95.07% 95.07%
=======================================
Files 582 582
Lines 46183 46183
Branches 14812 14812
=======================================
Hits 43907 43907
Misses 1516 1516
Partials 760 760
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
This was referenced Jul 14, 2026
This was referenced Jul 14, 2026
Closed
Closed
Closed
This was referenced Jul 15, 2026
Closed
Closed
Closed
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
.gittensory-miner.yml/.json(per-target-repo miner goal spec,MINER_GOAL_SPEC_FILENAMES) and.gittensory-ams.yml/.json(operator-local AMS execution policy,AMS_POLICY_SPEC_FILENAMES) — to.loopover-miner.*/.loopover-ams.*..envsibling and all four checked-in.examplefiles,.gitignoreentries, and — the one genuinely functional gap —docker-compose.miner.yml'senv_file:directive, which was still pointing at the old bare filename.prometheus/rules/alerts.yml(a runbook CLI-command example and.gittensory-ams.ymlpath mentions) discovered while verifying.Deliberately not touched (distinct, larger-blast-radius surfaces, left for a dedicated follow-up):
gittensory-miner-prediction/-portfolio-queue/-governor) and theup{job="gittensory"}scrape-job label in the same filegittensory-minermentions in testdescribe()/tmpdir-prefix strings across the suite (cosmetic, non-functional)Test plan
npm run typecheckcleannpx vitest run— 838 files / 16257 tests passed (2 pre-existing skips)npm run test:cigate green end-to-endnpm run docs:drift-check/npm run manifest:drift-checkclean