git: 3ac6260d69 - main - 2024q2 report: fix github report markup (for real this time)

Warner Losh <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
The branch main has been updated by imp:

URL: https://cgit.FreeBSD.org/doc/commit/?id=3ac6260d6950f16461eed8c572fb3e27b3cbc31f

commit 3ac6260d6950f16461eed8c572fb3e27b3cbc31f
Author:     Warner Losh <[email protected]>
AuthorDate: 2024-07-14 05:40:49 +0000
Commit:     Warner Losh <[email protected]>
CommitDate: 2024-07-14 05:41:22 +0000

    2024q2 report: fix github report markup (for real this time)
    
    Add spaces for markup. These were inadvertantly omitted form the last
    commit.
    
    Fixes: ee5c2fd57474
    Sponsored by: Netflix
---
 .../en/status/report-2024-04-2024-06/github.adoc   | 26 +++++++++++-----------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/website/content/en/status/report-2024-04-2024-06/github.adoc b/website/content/en/status/report-2024-04-2024-06/github.adoc
index f484bbbffe..fd1e9c160c 100644
--- a/website/content/en/status/report-2024-04-2024-06/github.adoc
+++ b/website/content/en/status/report-2024-04-2024-06/github.adoc
@@ -13,22 +13,22 @@ In general, pull requests should only be for things that are user-visible, add v
 
 Current status:
 
-* We are able to keep up with the pull requests doing everything by hand, but only if do it at least weekly.
-* We have discoverd the by-hand process is tedious and error-prone.
-* We can stage multiple pull requests in a testing branch so we can batch-up testing.
-* We can automatically land the result so merged pull requests show up as merged in github infrastructure.
+ * We are able to keep up with the pull requests doing everything by hand, but only if do it at least weekly.
+ * We have discoverd the by-hand process is tedious and error-prone.
+ * We can stage multiple pull requests in a testing branch so we can batch-up testing.
+ * We can automatically land the result so merged pull requests show up as merged in github infrastructure.
 
 We need help with automating the process:
 
-* Add automated testing that's context specific (for example, run igor over man pages).
-* Add build/install tests that test boot the resulting image.
-* Automate common tasks, like man page corrections, into staging process.
-* Add simple smoke testing for the staging branch for tier 1 architectures.
-* Investigate optionally integrating Jenkins testing to scale-up the size of changes we can accept.
-* Integrate with Bugzilla problem reports and Phabricator reviews.
-* Improve the submitter experience on github by automating common feedback to mistakes in the pull requests.
-* Create checklists for submitters to reduce errors.
-* Create better reporting about pull requests, especially the frequent contributors of good pull requests.
+ * Add automated testing that's context specific (for example, run igor over man pages).
+ * Add build/install tests that test boot the resulting image.
+ * Automate common tasks, like man page corrections, into staging process.
+ * Add simple smoke testing for the staging branch for tier 1 architectures.
+ * Investigate optionally integrating Jenkins testing to scale-up the size of changes we can accept.
+ * Integrate with Bugzilla problem reports and Phabricator reviews.
+ * Improve the submitter experience on github by automating common feedback to mistakes in the pull requests.
+ * Create checklists for submitters to reduce errors.
+ * Create better reporting about pull requests, especially the frequent contributors of good pull requests.
 
 We are coordinating on FreeBSD's Discord in the #github-hacking channel.
 Join us there to pitch in, or just chat about the project.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.