The output filters docs verbosely describe

• operators
• standard field

What i saw in the source but miss in the docs is

• negation
• operators
• dot notation

Also some examples of that might help.

Some streamlined quick try...

Simple filters

You can add simple filter expressions, reducing the r

This Issue serves as documentation for anticipated breaking changes in 3.0 and allows community feedback to drive the development process.

Breaking Changes 💔

• Do not re-export React from reactn. Have users just import React and ReactN Component/hooks from separate packages. This will help with the namespace conflicts with Component in TypeScript.
• Remove support for @reactn decora

I've personally just removed everything in ~/.travis while cleaning up because I don't still have the CLI installed at the moment, but I had trouble finding any succinct acknowledgement of the files (currently config.yml and travis.sh) in it, where they came from, and context on whether a user would want to back them up or not.

Some people assume these files, particularly ~/.travis/config.yml,

Ordinarily, I would try to update the docs myself, but I just don't have time.
I got hubcommander working today, but it was more effort than it should have been due to outdated documentation.

A few things I had issue with:

• In my org, I had to create a slack app in order to get a token. Then you must give the app the power to be a bot, and use the bot token for Oauth in order to get `rtm:str

See https://www.getzola.org/documentation/content/linking/ for ideas

We could go a step further and offer a variable on the post that allows someone to iterate over all the anchors and their titles. The downside is that I expect we'd only do this for markdown and not html because (1) trying to know if a page is html or not is dubious and (2) trying to infer anchors and their titles from rando

Add a short "Guide"/"How to play" section describing UI, basic game mechanics, agent types, effects, and abilities.

Use images and GIFs.

Check WarbitsManual.pdf as an example of a good guide.

Related to #420 ("Clarify how movement limits work")

According to GitHub's docs on CODEOWNERS, a code owner can be either a team name or a username. Bors doesn't support the latter.

I've noticed that there's a new warning that appears in recent build-logs (probably after travis-ci/travis-cookbooks#890 was merged):

/home/travis/filter.rb:43: warning: Insecure world writable dir /usr/local/clang-5.0.0/bin in PATH, mode 040777

Example build: https://travis-ci.org/travis-infrastructure/packer-build/jobs/299997045#L6

Perhaps you could add a word in the README file for saying that asciidoctor format is supported as well? (And what else?)

Also, apparently there’s no support for recurse option in awesome_bot but I was able to make it work with find -name "*.adoc" -print0 | xargs -0 awesome_bot in the .travis.yml file. Perhaps this would also deserve mention in the doc.

The issue template for this repo currently says:

Hello!

This isn’t the place for feature requests or bug reports. If that’s what you’ve come here for, please either visit our [public bug tracker](https://github.com/travis-ci/travis-ci/issues) or send us an email at support@travis-ci.org.

Otherwise, go ahead and delete this text :grimacing:

I read this as "this isn't the place

Adding documentation example of a working CI build using cirrus-ci.org (.cirrus.yml)

Now after improving the Algolia search for main documentation site cypress-io/cypress-documentation#2668 (which includes scrubbing these examples too, but with lower rank), it would be trivial to set up separate Algolia app and index to scrape the https://example.cypress.io/ site

How to set up scraping: https://glebbahmutov.com/blog/scrape-static-site-with-algolia/
Th

Suites like gcov works well if I execute many binaries (or the same binary with different arguments) in parallel, does kcov support this too? In particular, I'm interested in bash coverage.

For example, to have two scripts that source common.sh, and I execute them in two different shells, will the common.sh merged reports be OK? If not, what parts of kcov should be modified to support it?

Th

The documentation says that by default, CSV export generates a file "that is readable by Microsoft Excel in Europe, i.e., the default encoding is WINDOWS-1252 and the separator is ;".

I understand this is only a default, and it can be overridden using environment variables.

However, I suggest that the default should be changed to UTF-8 and the more standard comma-separated values, for the