Script updating gh-pages from 98ea1ad. [ci skip]

eckelcu · Jan 22, 2024 · fff70b9 · fff70b9
1 parent 25a53c9
commit fff70b9
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/draft-eckel-edm-find-code.html b/draft-eckel-edm-find-code.html
@@ -1361,7 +1361,7 @@ <h3 id="name-known-limitations">
             </ul>
 </li>
           <li class="normal" id="section-3.6-2.3">
-            <p id="section-3.6-2.3.1">The GitHub service, a GitHub repository associated with an I-D or RFC as recommended in <span><a href="#github-repository" class="internal xref">Section 3.1</a> (<a href="#github-repository" class="auto internal xref">Section 3.1</a>)</span>, and code referenced in a README as recommended in <span><a href="#readme" class="internal xref">Section 3.2</a> (<a href="#readme" class="auto internal xref">Section 3.2</a>)</span>, may get deleted or otherwise become unavailable.<a href="#section-3.6-2.3.1" class="pilcrow">¶</a></p>
+            <p id="section-3.6-2.3.1">The GitHub service, a GitHub repository associated with an I-D or RFC (see <span><a href="#github-repository" class="internal xref">GitHub Repository</a> (<a href="#github-repository" class="auto internal xref">Section 3.1</a>)</span>), and code referenced in a README (see <a href="#readme" class="auto internal xref">Section 3.2</a>), may get deleted or otherwise become unavailable.<a href="#section-3.6-2.3.1" class="pilcrow">¶</a></p>
 <ul class="normal">
 <li class="normal" id="section-3.6-2.3.2.1">
                 <p id="section-3.6-2.3.2.1.1">Collaboration with a code archiving service or creation of an IETF code archiving service could be helpful. Such a service need not have full code history, i.e., snapshots could be sufficient.<a href="#section-3.6-2.3.2.1.1" class="pilcrow">¶</a></p>

diff --git a/draft-eckel-edm-find-code.txt b/draft-eckel-edm-find-code.txt
@@ -318,9 +318,9 @@ Table of Contents
          been sponsored by ICANN.
 
    *  The GitHub service, a GitHub repository associated with an I-D or
-      RFC as recommended in Section 3.1 (Section 3.1), and code
-      referenced in a README as recommended in Section 3.2
-      (Section 3.2), may get deleted or otherwise become unavailable.
+      RFC (see GitHub Repository (Section 3.1)), and code referenced in
+      a README (see Section 3.2), may get deleted or otherwise become
+      unavailable.
 
       -  Collaboration with a code archiving service or creation of an
          IETF code archiving service could be helpful.  Such a service

diff --git a/index.html b/index.html
@@ -29,7 +29,7 @@ <h2>Preview for branch <a href="13-archiving-solution">13-archiving-solution</a>
       <tr>
         <td><a href="13-archiving-solution/draft-eckel-edm-find-code.html" class="html draft-eckel-edm-find-code" title="Find Code Related to an Internet-Draft or RFC (HTML)">find-code</a></td>
         <td><a href="13-archiving-solution/draft-eckel-edm-find-code.txt" class="txt draft-eckel-edm-find-code" title="Find Code Related to an Internet-Draft or RFC (Text)">plain text</a></td>
-        <td>same as main</td>
+        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://eckelcu.github.io/draft-eckel-edm-find-code/draft-eckel-edm-find-code.txt&amp;url_2=https://eckelcu.github.io/draft-eckel-edm-find-code/13-archiving-solution/draft-eckel-edm-find-code.txt" class="diff draft-eckel-edm-find-code">diff with main</a></td>
       </tr>
     </table>
     <script>