Look at new config page, click link.
Details
- Reviewers
epriestley - Group Reviewers
Blessed Reviewers - Commits
- rP27a243cd882f: Link to docs from metamta.mail-adapter config
Diff Detail
- Repository
- rP Phabricator
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
I got a SKIP STAGING Unable to determine repository for this change. warning, which I think was supposed to say "unable to determine staging repository...", which I'm not sure why, because it knows it's rP?
REPOSITORY To identify the repository associated with this working copy, arc followed this process: Configuration value "repository.callsign" is empty. This repository has no VCS UUID (this is normal for git/hg). Unable to determine the remote URI for this repository. This working copy is not associated with any repository. COMMIT RANGE If you run 'arc diff', changes between the commit: bddd1da053e86b1b Update Support diviner document ...and the current working copy state will be sent to Differential, because it is the merge-base of 'upstream/master' and HEAD, as specified in '.git/arc/default-relative-commit'. You can see the exact changes that will be sent by running this command: $ git diff bddd1da053e86b1b..HEAD These commits will be included in the diff: 54afd35e83ae3bea Link to docs from metamta.mail-adapter config MATCHING REVISIONS These Differential revisions match the changes in this working copy: D18259 Link to docs from metamta.mail-adapter config Reason: Commit message for '54afd35e83ae3bea' has explicit 'Differential Revision'. Since exactly one revision in Differential matches this working copy, it will be updated if you run 'arc diff'.
I cloned from github, and in a detached head. and origin is called upstream here.
Is your remote on GitHub named something other than origin? e.g., what does git remote get-url origin show?
If you name it origin, arc which should start identifying the repository correctly, staging should get pushed, and builds should wokr.
Or you can arc set-config --local repository.callsign P. Or you can branch from upstream with tracking, or branch from some branch which branches from upstream with tracking with tracking. But we don't trust remotes not named origin and not connected to the local branch.