GitHub repositories

Run forjex forge inside your application folder and choose the existing-project path. Create a new GitHub repository for an unpublished project, or select an existing remote.

A new GitHub repository is a destination for your files. To generate application files first, use a starter template.

Repository setup authenticates with GitHub. Your account needs permission to create a repository or write to the selected existing repository. Generating a local starter alone does not require this connection.

For account login, use forjex login and follow the browser flow. See authentication for token and sign-out options.

During repository setup, the CLI checks the build when a build command and the required dependencies are available. A new frontend starter without installed dependencies reports that local build verification was skipped. Commit messages can be reviewed and edited before the setup commits and pushes your files.

feat: add account settings form
fix: handle an expired session
docs: update setup instructions

Check git status and your .gitignore before the operation. The CLI stages files from the project directory during setup. For later changes, use the dedicated push command, which preserves existing staged selections and pushes the current branch.

forjex ai configure
forjex push --ai
forjex push -m "feat: add project search"

Run forjex ai configure or set your provider’s API-key environment variable to generate a message from staged text changes. Accept, edit, regenerate, or cancel before committing. Existing commits keep their messages. The push command does not run build checks; run your project checks before pushing.

Open the repository URL printed by the CLI and verify your files. If you enabled CI/CD, inspect the Actions tab. If you requested deployment, check the deployment result separately.

A successful GitHub push does not by itself confirm that tests passed or that the application is live.