This should be fixed in HEAD. Thanks for the exceptionally clear report, and let us know if you run into anything else.

The onscreen instructions for this adapter in the UI are also a bit out of date because the Google console has been updated since we wrote them. This is probably the next change to touch the provider, and should also look at modernizing the instructions.

The UI instructions about navigating the dashboard are also a little out of date since that UI has changed, although I was still mostly able to figure out what they meant. I'll leave a note on T5591 to update them when that gets fixed.

For completeness, T9953 / D14735 cleaned up an obscure rough edge on a narrow range of Git versions.

This is deployed and working properly.

I added some properties:

Yes, we can't help with this without better reproduction steps. In particular, I can't reproduce this. Here's what I did:

D14748 should fix the double feed stories.

The behavior of TITLE and VISIBILITY are also wrong: they emit the current body text, not the body text at the time the change was made.

I think this is happening because both the "Title" and "Body" transactions are emitting text:

This should be ready to go with the deployment tomorrow:

New blogs element is great :3

Oh, there are only two options and neither would break this.

Is Settings → Diff Preferences → Show Unified Diffs set to "On Small Screens" (the default) for you?

D14747 should fix this. I haven't pushed that yet, but I updated all the changelogs.

The URI scheme changed but this shouldn't fatal. I'll fix the fatal and then go fix the links in the changelogs, there are only like 6 of them or something.

In T9908#148607, @epriestley wrote:

It doesn't seem to work properly if I try to comment and also change the status of a task. The comment appears but the task status remains unchanged.

I can't reproduce this. Does it reproduce for you on this install?

In T9908#148608, @chad wrote:

A minor usability issue as well... If you click on the "Add Action" drop down and continually press the down key then you end up adding every action. Maybe we can just disable this behavior?

This doesn't reproduce for me, can you provide more details? It just goes down the select list (and I have to hit <enter> to make it trigger)

I think this should now be fixed in HEAD. Let us know if we missed anything, and thanks for the report.

It doesn't seem to work properly if I try to comment and also change the status of a task. The comment appears but the task status remains unchanged.

I noticed a few minor issues after deploying this on our install.

So you haven't actually reproduced this yourself? Is it possible that the user mistook xxxxx as uncensored credentials? Can you try reproducing it directly?

I should note that we're running the latest version of Git (2.6.3) which could be the culprit. From my superficial inspection of the code, it appears that the output of git fetch is simply reflected.

In your report, you say <user email address> -- is the login username for this user a string including "@"? Does the UI print out a message like this?

Until we have such a tool, you can revoke keys like this:

I think this is worth improving. However, I think it is not a very important feature in situations where things are set up reasonably well (not too many lint false positives, fairly fast tests or server-side CI), and that fixing these problems will have a lot of other benefits in cases where they aren't working well. That is, this should be more like a "nice-to-have" that saves you a few seconds once a week, not something you're hitting on >50% of revisions.

Can I set looks an intern on this?

Although timeline is now linked, I think feed still isn't linked?

What version of Phabricator are you running? (You can find this in Config → Versions for recent versions.)

Do you have the public key (or the private key), or do you just know which user has a compromised key but not know which key is compromised?

I can't reproduce that. Here's a search using "Path", which seems to work correctly:

This request does not describe a root problem.

I eventually got this live. blog.phacility.com is a little plain now, but seems to work fine:

@andrew-dixon Sorry, there's no secret internal tracker full of juicy updates that we're hiding from the public. If we haven't updated a task, there aren't any updates on it. See Planning for a little more discussion on this in general.

• Send rules upstream for now (like with the Korean rules).
• We'll probably make this modular eventually.

This has been in production for a while and seems to be working correctly. New rules are:

Closing this out since there's nothing actionable here.

I'm planning to just remove skin support in T9897.

Assuming this is in good shape now.

I believe this was fixed by D14511.

This was fixed in connection with T9825.

I can't reproduce this. Here's what I did:

Briefly, T9529 discusses some server-side system running on revisions that's live in your environment, presumably. Its current behavior is something like this:

T8378 discusses a milder case of this sort of thing but I think the logic here applies to it as well.

I think T8405 and this are both basically discussing the same use case, which I understand to be: