Page MenuHomePhabricator

Link to docs from metamta.mail-adapter config
ClosedPublic

Authored by avivey on Jul 21 2017, 12:38 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 28, 2:13 AM
Unknown Object (File)
Tue, Nov 26, 2:03 PM
Unknown Object (File)
Sat, Nov 23, 4:25 AM
Unknown Object (File)
Sat, Nov 23, 4:13 AM
Unknown Object (File)
Wed, Nov 20, 9:24 PM
Unknown Object (File)
Nov 5 2024, 11:58 PM
Unknown Object (File)
Nov 5 2024, 11:58 PM
Unknown Object (File)
Nov 5 2024, 11:58 PM
Subscribers

Details

Test Plan

Look at new config page, click link.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jul 21 2017, 12:40 AM

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?

Yeah, I renamed origin to upstream, and (it's the only remote right now).

Did I go to far over the bend for this?

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.

Renamed the upstream to check sanity

Ok, so that was one hack too many :)

This revision was automatically updated to reflect the committed changes.