Skip to content

docs(rfc): host in change ID URI format#326

Closed
JamyDev wants to merge 1 commit into
mainfrom
jamy/rfc-host-in-change-id-uri
Closed

docs(rfc): host in change ID URI format#326
JamyDev wants to merge 1 commit into
mainfrom
jamy/rfc-host-in-change-id-uri

Conversation

@JamyDev

@JamyDev JamyDev commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds an RFC documenting the design decision to embed the host (domain/port) in GitHub, GHES, and Phabricator change ID URIs. The old URI format encoded everything about a change except which server it lives on, making it impossible to distinguish changes across multiple instances of the same provider type (e.g. multiple GHES instances). The RFC covers the new URI format, migration strategy, stacked-change validation, and alternatives considered.

Test Plan

Existing CI/Build validation

Revert Plan

git revert

Jira Issues

API Changes

No API changes

Monitoring and Alerts

Standard monitoring via existing dashboards

🤖 Generated by minion
Co-Authored-By: minion-bot noreply@minion.uber.com
Co-Authored-By: jamy@uber.com
Agent: claude-code | Task: 87c9d30e-c740-416a-9bce-201e86b2f14c

View your task: https://minion.uberinternal.com/task/87c9d30e-c740-416a-9bce-201e86b2f14c

Summary:
Intent:
- Embed the target host (domain/port) in every change ID URI so change identity is self-contained across multiple GitHub/GHES/Phabricator instances

Changes:
- Added RFC at doc/rfc/submitqueue/host-in-change-id.md covering the new URI format, migration path, stacked-change validation, and alternatives considered
- Updated doc/rfc/index.md to link the new RFC

## Summary

Adds an RFC documenting the design decision to embed the host (domain/port) in GitHub, GHES, and Phabricator change ID URIs. The old URI format encoded everything about a change except which server it lives on, making it impossible to distinguish changes across multiple instances of the same provider type (e.g. multiple GHES instances). The RFC covers the new URI format, migration strategy, stacked-change validation, and alternatives considered.

## Test Plan

Existing CI/Build validation

## Revert Plan

git revert

## Jira Issues

## API Changes

No API changes

## Monitoring and Alerts

Standard monitoring via existing dashboards

🤖 Generated by minion
Co-Authored-By: minion-bot <noreply@minion.uber.com>
Co-Authored-By: jamy@uber.com
Agent: claude-code | Task: 87c9d30e-c740-416a-9bce-201e86b2f14c

View your task: https://minion.uberinternal.com/task/87c9d30e-c740-416a-9bce-201e86b2f14c

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@JamyDev JamyDev closed this Jul 10, 2026
@JamyDev JamyDev deleted the jamy/rfc-host-in-change-id-uri branch July 10, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant