Documentation, texinfo manual, readme generation

.github/flake.nix

@@ -95,6 +95,13 @@
                   # needed by your repo after cloning.
                   epkgs.elpaPackages.project
                   epkgs.melpaPackages.auto-compile
+                  epkgs.melpaPackages.license-templates
+
+                  # Optionally override derivations.
+                  # melpaPackages.weechat.overrideAttrs(old: {
+                  #   # probably you want to override the src attribute
+                  #   patches = [ ./weechat-el.patch ];
+                  # })
                 ]))
             ];
           });

.github/pull_request_template.md

@@ -1,12 +1,13 @@
 ## Pull Requests
 
-Generated changes to the flake.lock should be kept in a separate commit for the
-reviewer.  Title your commit as "generated".
+**Generated** changes to the documentation and flake.lock should be kept in a
+separate commit for the reviewer.  Title your commit as "generated".
 
 Keeping these changes isolated in specific commits makes it much easier to pull
-in your changes in parallel with other features.  Maintainers may harvest your
-changes.  We only guarantee to preserve authorship, signature, and sign-off in
-the git log.
+in your changes in parallel with other features.
+
+Maintainers may harvest your changes.  We only guarantee to preserve authorship,
+signature, and sign-off in the git log.
 
 ### Creating pull requests
 
@@ -18,3 +19,14 @@ the git log.
    checkbox)
 1. Once the pull request has been approved, you will be thanked and observe your
    changes applied with authorship, signature, and sign-off in the git log
+
+### Reminder about PR access to upstream CI
+
+Pull-requests run with the `pull_request_target` Github Actions configuration.
+Your PR can access secrets, but it run's the **upstream's** CI, not the CI
+changes you are submitting.
+
+If you need to make changes to CI itself in order to pass checks, you will need
+to work with the repository's owner.  The owner will pull the branch into a
+non-master branch.  There, they can trigger the CI manually with the branch's
+own configuration using `workflow_dispatch` in the Actions tab.

.github/run-shim.el

@@ -2,7 +2,7 @@
 
 ;; Copyright (C) 2022 Positron Solutions
 
-;; Author:  <author>
+;; Author:  Positron Solutions <[email protected]>
 
 ;; Permission is hereby granted, free of charge, to any person obtaining a copy of
 ;; this software and associated documentation files (the "Software"), to deal in

.github/workflows/ci.yml

@@ -43,6 +43,8 @@ jobs:
         os: [ubuntu-latest, macos-latest]
         emacsPkg: [ emacs, emacsGit, ]
     runs-on: ${{ matrix.os }}
+    # If you update steps, be sure to update the approved actions list in the
+    # manual and in your repositories!
     steps:
       - uses: actions/[email protected]
         with:

.gitignore

@@ -3,4 +3,5 @@
 ***autoloads.el
 **trash
 **~
-**.~undo-tree
+**.~undo-tree
+/docs/manual.info