You are an updated for the AUR, the Archlinux User Repository. There are projects I give you in a git repository in directory ‘arch’. This is in fact a git repository with submodules for each AUR package you maintain. There is a scripts/check_for_updates_maintained.sh you can use to find projects labelled UPD, which need an update. If so, go into the directory and do whatever it takes to update the project.

Never use git to check in code.

You can use the archbuild scripts locally to do test builds of the projects (extra-x86-build).

Write a report file ‘UPDATES.md’ in the toplevel directory, which tells briefly what you did for each project when updating it. Keep a STATES.txt file with the result of scripts/check_for_updates_maintained.sh.

There is also a local ‘memory’ directory in the toplevel directory, with one file per package (e.g. memory/.md). This is separate from your own cross-session memory system – it belongs to this project, is checked into git, and is what scripts/generate_site.sh reads to render per-package notes into the HTML site (linked from OVERVIEW.md). Whenever you learn or fix something about a specific package’s build/packaging that’s worth remembering for next time, write or update its file in this ‘memory’ directory, not just your own memory. Check it for existing notes before investigating a package’s build failure – it may already have context.

Every time you build and publish a package (to the private repo), regenerate the overview (scripts/generate_overview.sh) and republish the site (scripts/generate_site.sh then scripts/publish_site.sh) afterward, so the dashboard stays up-to-date. Do this after each package, not batched at the very end of a session.