Cleanup whitespace in markdown table

Doesn't impact the rendered version, but makes the plain-text much easier to read
This commit is contained in:
Benjamin Hipple 2020-02-16 19:09:25 -05:00
parent 5dee76e9b2
commit 2d4b91fb44

View file

@ -17,12 +17,12 @@ as well as other changes.
Example messages and the builds: Example messages and the builds:
|Message|Automatic Build| | Message | Automatic Build |
|-|-| |-----------------------------------------------------------------------|----------------------------------------------------------|
|`vim: 1.0.0 -> 2.0.0`|`vim`| | `vim: 1.0.0 -> 2.0.0` | `vim` |
|`vagrant: Fix dependencies for version 2.0.2 `|`vagrant`| | `vagrant: Fix dependencies for version 2.0.2 ` | `vagrant` |
|`python36Packages.requests,python27Packages.requests: 1.0.0 -> 2.0.0`|`python36Packages.requests`, `python27Packages.requests`| | `python36Packages.requests,python27Packages.requests: 1.0.0 -> 2.0.0` | `python36Packages.requests`, `python27Packages.requests` |
|`python{2,3}Packages.requests: 1.0.0 -> 2.0.0`|_nothing_| | `python{2,3}Packages.requests: 1.0.0 -> 2.0.0` | _nothing_ |
If a PR is opened with many commits, it will create a single build job If a PR is opened with many commits, it will create a single build job
for all of the detected packages. If a PR is opened and many commits for all of the detected packages. If a PR is opened and many commits
@ -221,9 +221,9 @@ config.known-users.json, run `./scripts/update-known-users.sh`.
In case you have a non-trivial setup on Linux, make sure that the ofborg In case you have a non-trivial setup on Linux, make sure that the ofborg
user has access to `dev/kvm`, as it is needed for running tests. user has access to `dev/kvm`, as it is needed for running tests.
If you want to run multiple builder instances on the same physical If you want to run multiple builder instances on the same physical
machine please make sure they use different configs with different machine please make sure they use different configs with different
instance identity (same username/password is OK) and different instance identity (same username/password is OK) and different
repository paths. Running two builders with the same config risks data repository paths. Running two builders with the same config risks data
corruption. corruption.