Jens/ForgeFlow-Public
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Publish curated ForgeFlow source from 63022ccf9a37242d573297c8ce7f15db61acc34e
ForgeFlow quality gate / secret-scan (push) Successful in 4s
Details
ForgeFlow signed release / release (push) Failing after 18m45s
Details
ForgeFlow quality gate / quality (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Public Source Publisher committed 2026-09-30 21:27:28 +00:00
1 parent bdfcc1585d
commit 04cbfccbdb
19 files changed
+233 -77
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+5 -5
View File
@@ -5,9 +5,9 @@
ForgeFlow is a Windows desktop application for teams that use Git, Gitea and self-hosted Docker or Unraid servers. It brings local changes, remote commits and the exact revision running on a server into one workspace, then guides review, commit, push, deployment and verification.
> **Public-source edition:** This repository contains reviewed source files from a private canonical repository. It does not yet host signed Windows releases. `PUBLIC_SOURCE_MANIFEST.json` identifies the exact source revision and file hashes; private Git history is not included.
> **Public-source edition:** This repository contains reviewed source files from a private canonical repository. Stable Windows releases are built from this curated source and carry an Ed25519-signed publisher manifest. `PUBLIC_SOURCE_MANIFEST.json` identifies the exact source revision and file hashes; private Git history is not included.
**Downloads:** Existing signed Windows releases remain at [the legacy ForgeFlow release page](https://gitea.itworx.tech/Jens/ForgeFlow/releases/latest) during the public-repository transition. The [curated public source](https://gitea.itworx.tech/Jens/ForgeFlow-Public) is separate; it will become the release destination only after signing and update compatibility are verified.
**Downloads:** Get current Windows releases from [ForgeFlow-Public](https://gitea.itworx.tech/Jens/ForgeFlow-Public/releases/latest). The [legacy release page](https://gitea.itworx.tech/Jens/ForgeFlow/releases/latest) stays available while older installations move to the new update endpoint.
## See the workflow
@@ -37,12 +37,12 @@ ForgeFlow distinguishes a matching commit from a healthy deployment. It keeps in
### Install the Windows app
1. Download an installer or portable executable from the [published release page](https://gitea.itworx.tech/Jens/ForgeFlow/releases/latest).
1. Download an installer or portable executable from the [published release page](https://gitea.itworx.tech/Jens/ForgeFlow-Public/releases/latest).
2. Launch ForgeFlow and complete the setup wizard.
3. Add your Gitea URL, a token with the required repository permissions, and the local folders to scan.
4. Optionally add a Docker or Unraid host, then use **Scan servers** to review detected workloads.
The packaged updater checks a release against the exact remote commit, its SHA-256 checksum and the embedded Ed25519 publisher key. Existing installations continue to use the legacy release endpoint until the migration is qualified.
The packaged updater checks a release against the exact published release commit, its SHA-256 checksum and the embedded Ed25519 publisher key. Existing installations receive the 0.10.16 bridge release from the legacy endpoint; after installation, the default update endpoint changes to ForgeFlow-Public.
### Explore with example data
@@ -81,6 +81,6 @@ npm run acceptance
`npm run check` performs source verification, linting and tests. Browser acceptance and Windows packaging are separate release gates. `src/main/` contains desktop services and IPC, `src/renderer/` contains the UI, `src/shared/` holds shared policies, `scripts/` contains validation and release tooling, and `tests/` covers core behavior.
The private canonical repository publishes a reviewed, content-only snapshot to `ForgeFlow-Public`. Its manifest records the source revision; private Git history and operational evidence are excluded. Binary release publication remains manual during the endpoint transition.
The private canonical repository publishes a reviewed, content-only snapshot to `ForgeFlow-Public`. Its manifest records the source revision; private Git history and operational evidence are excluded. A version change in the curated public repository starts the Windows quality, build, signing and release workflow. Source-only changes do not publish a new binary version.
ForgeFlow is available under the [MIT License](LICENSE). Report security issues through [SECURITY.md](SECURITY.md).