OK, looks like this is just a case of miss-reading the docs:

• name (optional) Text summarizing the lint message. For example, "Syntax Error".

name in the regex does not mean "Name of linter" but "Title of error".

It's my own script. I haven't found anything like this in the sources. I also haven't found any hints how to integrate`arc lint` without pain (no --target option like for arc unit).

cat is slow to appear

I see cat :)

ok now cat is in feed

hmm, cat no show in feed

It's doing it again now...

What made the translation from the string-after-regex to the harbormaster json structure in your example?

Yes, triggers sound like they'll do the job. Not to say search and filterability still wouldn't be handy in more ad-hoc cases. Triggers require foresight.

I've just noticed that arc lint --everything output summary gives me this:

I'll try to give an example which makes clear that linter message is not meant to be linter name.

Talk to your administrator, they've changed your installs permissions. If you have other questions on Phabricator, please use Conpherence or Ponder. Feature Requests are for ... well feature requests.

Unfortunately this probably isn't something we'd pursue in the upstream, so we won't likely take code into the upstream for it. We allow people to share things like this though on the Community Resources page in Phriction

T5055 also covers distribution of linters/etc via arcanist as a package manager.

OK. to decrease the deploy cost. i would like to contribute the project. try my best to do this work. I am not ask you provide it for me . Is it an opensource project? Every one can contribute it ? but i still need your guide. if i want implements. what the problem block us do the work?

T6012 covers composer, T4200 covers alternate installation methods. In general, I'd assume you're installing all developer tools (if you're a large org) via some scripts, and scripting the installation of arc/git, is trivial. arc upgrade can be ran locally to keep developers up to date.

Not really, I'm still not sure what the root problem is. It mostly sounds hypothetical. In general you're asking us to do weeks of work to save 1 engineer 5 seconds, 1 time over the course of their job. At least, it seems like if those few seconds are so vital, that you'd script all developer tool installations with one script. I don't see what 2 repositories vs. 1 solves.

@chad. i tried to explain why i post the feature request. it it ok? valid for feature request requirement?

You didn't see this at the top of the Feature Request form?

Well, i have not found a feature request template. but i tried to explain why i post this feature request.

See Contributing Feature Requests for what information is required for a feature request.

Looked like there was some feed story grouping discussion in there

This is just a copy of a feature already discussed in T11432, right? Closing this in favor of that, which is already a better and more complete discussion of this request with context.

It's currently unclear to me if this is a bug report or feature request. The code appears to be working as intended, and adding the description to the property table would be an added feature.

Please follow all guidelines in Contributing Bug Reports. These are required on all bug reports.

Moving to a sandbox instance.

Moving to a sandbox instance.