Update .arcconfig to point at https://phabricator-dev.allizom.org/ and change the repository.callsign to MOZILLACENTRAL. This switches Arcanist configuration to the development Phabricator instance while leaving history.immutable set to false.
Details
Details
Diff Detail
Diff Detail
- Repository
- rMOZILLACENTRAL mozilla-central
- Branch
- HEAD
Event Timeline
Comment Actions
Summarization
Intent
The changes aim to update the Arcanist configuration file (.arcconfig) to point to Mozilla's development Phabricator instance instead of the production instance. This is part of Bug 1855045, which requests switching the Arcanist setup to use the development environment at phabricator-dev.allizom.org.
Solution
The solution modifies two configuration values in .arcconfig: the phabricator.uri is changed from the production URL (https://phabricator.services.mozilla.com/) to the development URL (https://phabricator-dev.allizom.org/), and the repository.callsign is changed from FIREFOXAUTOLAND to MOZILLACENTRAL to match the corresponding repository identifier on the development instance. The history.immutable setting is left unchanged at false.
Please use / reactions on inline comments to provide feedback. This will have a significant impact on the quality of future reviews.
| .arcconfig | ||
|---|---|---|
| 2 | This change redirects all Arcanist/moz-phab submissions from the production Phabricator instance to the dev instance. If this lands on autoland/mozilla-central, every developer running moz-phab submit will unknowingly send their patches to the dev server. Add a clear comment in the commit message (or here) explaining whether this is a temporary change and reference Bug 1855045 so it can be tracked and reverted. | |
| 3 | The callsign is changing from FIREFOXAUTOLAND to MOZILLACENTRAL. Since this is the autoland repository's .arcconfig, the callsign should match the repository on whichever Phabricator instance is being targeted. Verify that MOZILLACENTRAL is the correct callsign for this repo on the dev instance—submitting with the wrong callsign will cause patch landing failures. | |