aboutsummaryrefslogtreecommitdiff
path: root/docs/announcements
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-02-12 12:06:33 -0600
committerCraig Jennings <c@cjennings.net>2026-02-12 12:06:33 -0600
commit5df64c76d386fd2de863d21a2b1269d53e1a39f9 (patch)
tree7ed3e3a4cccbafe109ff8c87ec8b1e3cfb120141 /docs/announcements
parent24a681c0696fbdad9c32073ffd24cf7218296ed2 (diff)
downloadarchangel-5df64c76d386fd2de863d21a2b1269d53e1a39f9.tar.gz
archangel-5df64c76d386fd2de863d21a2b1269d53e1a39f9.zip
fix: archzfs key prompt hang, test false positive, add local distribution
- Change archzfs SigLevel to Never (pacstrap -K empty keyring caused interactive GPG prompt blocking unattended installs) - Fix pgrep matching avahi-daemon's [archangel.local] in full-test.sh - Bump install timeout to 30min for DKMS builds - Add ~/downloads/isos and archsetup inbox to build-release distribution - Sync templates
Diffstat (limited to 'docs/announcements')
-rw-r--r--docs/announcements/the-purpose-of-this-directory.org18
1 files changed, 18 insertions, 0 deletions
diff --git a/docs/announcements/the-purpose-of-this-directory.org b/docs/announcements/the-purpose-of-this-directory.org
new file mode 100644
index 0000000..ae3f756
--- /dev/null
+++ b/docs/announcements/the-purpose-of-this-directory.org
@@ -0,0 +1,18 @@
+The purpose of this directory is to contain one-off instructions for every project using these templates.
+
+Example:
+- restructing of the claude-specific directories.
+- announcements of new workflows and how to use them.
+- one-off topics to be discussed with Craig when the templates are sync'd.
+
+How The Directory Is Used
+- Craig will decide that all projects will need to perform an action (reorganizing files, adding info to NOTES or protocols, removing unused workflows)
+- Craig will add the instructions as a file in this directory
+- When the project syncs templates, they will inherit new files in the directory
+- They will discuss the instructions with Craig to ensure he knows they have understood the instructions and have the opportunity to ask any clarifying questions before executing the instructions.
+- They will then execute the instructions.
+- They will inform Craig of the results of executing the instructions (success, failure, and any observations).
+- Typically, they will delete the instructions when complete unless the instructions explicitly state to do otherwise.
+
+
+NOTE: This file should always remain in the directory for future reference. This file may be overwritten by a template sync, but should never otherwise be deleted by claude.