Wed, Nov 13
I've marked D20905 as resolving this. This isn't really "resolved" completely, but T13454 has a better description of what the problems are and why they're difficult. Our behavior is, at least, substantially better than it was before.
Nov 11 2019
Jan 11 2018
I have been trying to see about another way to do this until this is added (if it is I should say). We are finally getting ready to move to Phabricator, and I was hoping there was at least a shortcode or something I can use. Currently what I was trying to do was paste the query URL for a particular project's Passphrase credentials. What we were going to try was getting the query for whichever project's passwords, copying it, and adding it to the Project as a custom link.
Oct 9 2017
Sep 5 2017
Apr 17 2017
Feb 17 2017
Feb 15 2017
Jan 2 2017
Nov 15 2016
Thank you, that was a very quick resolution, I just had the time to refresh the page !
Aug 25 2016
GHC would also find support for importing keys from Github useful; we are currently working on rolling out a Diffusion-hosted staging area for use with Harbormaster but the need for contributors to submit their key to yet another Phab feels like unnecessary friction.
Jul 5 2016
May 26 2016
You can talk to Passphrase over Conduit; you need to give credentials access by clicking the "Allow Conduit Access" action.
May 25 2016
This is conceptually reasonable, but likely years away. We ship no native code right now. Although there are many Phabricator applications which could take advantage of an optional OS client (for example, to make it easier to upload screenshots or access files) the pathway from where we are now to building one is a very long one, and none of these use cases are near the top of our priority list.
May 10 2016
I am waiting tag(s) field for credentials too.
May 1 2016
Apr 14 2016
Should be fixed in HEAD of master. Thanks for the report!
Apr 12 2016
Apr 7 2016
You shouldn't be getting an exception.
It's the git master from yesterday, wasn't sure if it's a bug or an installation/config error.
What revision is your install running on? If it's recent then this might be a legitimate bug and should be reported.
I tried to add a new credential.
Mar 25 2016
Sounds good, let us know if you run into anything else.
Latest version seems to have fixed this. Sorry for the noise, and thanks for building such an awesome software.
For completeness, T10651 is the earlier report.
(fantastic bug reporting, otherwise)
I think that stuff isn't linking because someone is pushing their own branches to the upstream staging repository, making the commits ambiguous. That is, e3f89279f912 is ambiguous as either rPe3f89279f912 or rSTAGINGe3f89279f912.
rPe3f89279f912 should have resolved this, I believe.
Doh. Give me a minute, testing with 3493d9d5138e0a630624bced548090163ce9be8a now.
Your install is out of date.