summaryrefslogtreecommitdiff
path: root/contributors
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2020-08-06 10:51:43 -0700
committerGitHub <noreply@github.com>2020-08-06 10:51:43 -0700
commit967a3fad0fdc795f9646ca9b5b87591864c59fae (patch)
treef55fbf665787e513fdea2182b1698f8268084e5c /contributors
parentadaeeacf66bc3a2eacde89896dbfe9a8c4e85767 (diff)
parent4d93fad4c03d2016adfec7232603312005c83115 (diff)
Merge pull request #4998 from shubhamdang/patch-1
Fixed formatting of automation.md
Diffstat (limited to 'contributors')
-rw-r--r--contributors/devel/automation.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/devel/automation.md b/contributors/devel/automation.md
index bc0de2ec..8e3e1fed 100644
--- a/contributors/devel/automation.md
+++ b/contributors/devel/automation.md
@@ -11,7 +11,7 @@ processes.
This project formerly used a Submit Queue, it has since been replaced by
[Tide](https://git.k8s.io/test-infra/prow/cmd/tide).
-#### Ready to merge status
+### Ready to merge status
A PR is considered "ready for merging" by Tide if it matches the set
of conditions listed in the [Tide dashboard](https://prow.k8s.io/tide).
@@ -40,7 +40,7 @@ reply with the `/ok-to-test` command on a single line to begin CI testing.
## FAQ:
-#### How can I ask my PR to be tested again for test failures?
+### How can I ask my PR to be tested again for test failures?
PRs should only need to be manually re-tested if you believe there was a flake
during the original test. It would be good to file flakes as an