linkerd2

Author SHA1 Message Date

Author	SHA1	Message	Date
Joakim Roubert	8d19b4055b	Improve shellscript portability by using /bin/env (#4628 ) Using `/bin/env` increases portability for the shell scripts (and often using `/bin/env` is requested by e.g. Mac users). This would also facilitate testing scripts with different Bash versions via the Bash containers, as they have bash in `/usr/local` and not `/bin`. Using `/bin/env`, there is no need to change the script when testing. (I assume the latter was behind `c301ea214b (diff-ecec5e3a811f60bc2739019004fa35b0)`, which would not happen using `/bin/env`.) Signed-off-by: Joakim Roubert <joakimr@axis.com>	2020-06-19 15:49:29 -04:00
Joakim Roubert	6b36934143	markdownlint: Use /bin/sh instead of /bin/bash (#4447 ) The nice and clean markdownlint scripts use no bash-specific functionality. Hence they could be run with /bin/sh instead. On e.g. Debian-based systems /bin/sh is dash which has 1/10 of bash's footprint. Signed-off-by: Joakim Roubert <joakimr@axis.com>	2020-05-20 16:36:53 -07:00
Kevin Leimkuhler	d99c1486ba	Lint all markdown files in CI (#4402 ) ## Motivation linkerd/rfc#22 ## Solution Use the [markdown-lint-action](https://github.com/marketplace/actions/markdown-linting-action) to lint all `.md` files for all pull requests and pushes to master. This action uses the default rules outlined in [markdownlint package](https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md). The additional rules are added are explained below: - Ignore line length lints for code blocks - Ignore line length lints for tables - Allow duplicate sub-headers in sibling headers (e.g. allowing multiple ## Significant headers in `CHANGES.md` as long as they are part of separate release headers) Signed-off-by: Kevin Leimkuhler <kevin@kleimkuhler.com>	2020-05-19 23:03:50 -07:00

Joakim Roubert

8d19b4055b

Improve shellscript portability by using /bin/env (#4628 )

Using `/bin/env` increases portability for the shell scripts (and often using `/bin/env` is requested by e.g. Mac users). This would also facilitate testing scripts with different Bash versions via the Bash containers, as they have bash in `/usr/local` and not `/bin`. Using `/bin/env`, there is no need to change the script when testing. (I assume the latter was behind c301ea214b (diff-ecec5e3a811f60bc2739019004fa35b0), which would not happen using `/bin/env`.)

Signed-off-by: Joakim Roubert <joakimr@axis.com>

2020-06-19 15:49:29 -04:00

Joakim Roubert

6b36934143

markdownlint: Use /bin/sh instead of /bin/bash (#4447 )

The nice and clean markdownlint scripts use no bash-specific
functionality. Hence they could be run with /bin/sh instead. On e.g.
Debian-based systems /bin/sh is dash which has 1/10 of bash's footprint.

Signed-off-by: Joakim Roubert <joakimr@axis.com>

2020-05-20 16:36:53 -07:00

Kevin Leimkuhler

d99c1486ba

Lint all markdown files in CI (#4402 )

## Motivation

linkerd/rfc#22

## Solution

Use the [markdown-lint-action](https://github.com/marketplace/actions/markdown-linting-action) to lint all `.md` files for all pull requests
and pushes to master.

This action uses the default rules outlined in [markdownlint
package](https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md).

The additional rules are added are explained below:
- Ignore line length lints for code blocks
- Ignore line length lints for tables
- Allow duplicate sub-headers in sibling headers (e.g. allowing multiple ##
  Significant headers in `CHANGES.md` as long as they are part of separate
  release headers)

Signed-off-by: Kevin Leimkuhler <kevin@kleimkuhler.com>

2020-05-19 23:03:50 -07:00

3 Commits