Git and change control

Git records the history of your project. Nocturnal brings that history and your current changes beside the agents doing the work.

Review before you save

Open the Git view to see the current branch and uncommitted files. Inspect a file’s diff to understand the additions and removals. Review the scope before committing; an agent’s summary is useful context alongside the actual changes.

If the folder does not have a repository, Create repository helps you establish Git and a GitHub remote. Choose the repository’s visibility deliberately and make sure GitHub is connected first.

Commits and push

A commit saves a snapshot in local Git history. Write a message explaining the change and review the files included. Pushing sends your commits to the remote repository, such as GitHub.

The status view shows incoming and outgoing commits so you can see when local and remote history differ. A local commit and a successful push are distinct steps.

Nocturnal does not branch for you

An agent works on the branch your repository is already on and leaves what it wrote in the working tree. It does not create a branch, switch a branch, or commit — that stays your call, in the Git view, the same as any change you make by hand.

If you want a change on its own branch, create the branch yourself before or after the work, as below.

Branches and pull requests

A branch gives a change its own line of development. Create or switch a branch from Git. When the change is ready, push it and open a pull request for review and checks before merging.

Follow your repository’s branch protections and review process. Nocturnal provides the controls; it does not automatically add protection rules to GitHub.

Issues, checks, and deployment

Use the Issues view to manage your GitHub queue and prepare an agent task. Inspect existing GitHub Actions in CI, then use your configured deployment workflow when the change is ready.

Issues · Continuous integration · Deployment.

Git history and release notes

Nocturnal’s version log is a readable account of what shipped. It complements Git commits and tags; it is not a backup of your repository or a rollback operation. Versions and changelogs.