mrhavens/git-sigil
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Generated GITFIELD.md at 2025-06-09T20:30:45Z

Browse source
This commit is contained in:
Mark Randall Havens 2025-06-09 15:33:04 -05:00
parent a493713786
commit 72f630be8d
1 changed files with 6 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
GITFIELD.md
View file

@ -79,11 +79,14 @@ This multi-repository approach, bolstered by Forgejo’s sovereign hosting, refl
## 📜 Metadata and Logs
- **Metadata Files**: Each platform generates a metadata snapshot in the `.gitfield` directory (e.g., `github.sigil.md`, `gitlab.sigil.md`, `remember.sigil.md`, `codeberg.sigil.md`, `gitea.sigil.md`, etc.), capturing commit details, environment information, and hardware fingerprints.
- **Push Log**: The `.gitfield/pushed.log` file records the date, time, and RID/URL of every push operation across all platforms, providing a transparent audit trail.
- **Canonical Metadata**: The canonical repository is declared in [`.gitfield/canonical.meta`](./.gitfield/canonical.meta) (machine-readable JSON) and [`.gitfield/canonical.md`](./.gitfield/canonical.md) (human-readable Markdown).
- **Index Manifest**: A full manifest of remotes, commit details, and sync cycles is available in [`.gitfield/index.json`](./.gitfield/index.json).
- **Well-Known Metadata**: SEO-friendly metadata with Schema.org JSON-LD is available in [`.well-known/gitfield.json`](./.well-known/gitfield.json).
- **Push Log**: The `.gitfield/pushed.log` file records the date, time, commit hash, and RID/URL of every push operation across all platforms, providing a transparent audit trail.
- **GitField Directory**: The `.gitfield` directory contains additional metadata and platform-specific sigils (e.g., `github.sigil.md`). See [`.gitfield/README.txt`](./.gitfield/README.txt) for details.
- **Recursive Sync**: The repository is synchronized across all platforms in a recursive loop (three cycles) to ensure interconnected metadata captures the latest state of the project.
- **Push Order**: The repository is synchronized in the following order: **Radicle → Forgejo → Codeberg → Gitea → GitLab → Bitbucket → GitHub**. This prioritizes Radicle’s decentralized, censorship-resistant network as the primary anchor, followed by Forgejo’s sovereign, self-hosted infrastructure, Codeberg’s community-driven platform, Gitea’s lightweight efficiency, GitLab’s robust DevOps features, Bitbucket’s enterprise redundancy, and GitHub’s broad visibility, ensuring a resilient and accessible metadata chain.
---
_Auto-generated by `gitfield-sync` at 2025-06-09 14:43:29 (v1.0)._
_Auto-generated by `gitfield-sync` at 2025-06-09T20:30:45Z (v1.1)._